practical-asp-net / blazortailwindtemplate Goto Github PK

The latest version of Tailwind ships with a brand new Just-In-Time mode.

https://tailwindcss.com/docs/just-in-time-mode

In theory this would remove the need to compile the Tailwind css file on every build but it's not yet clear (to me at least) how it works and how (or indeed if) it could be used with dotnet.

The template is currently only available for Blazor WASM, would be useful to be able to create Blazor Server projects too.

Fixup CI workflows a bit to optimize:

• Move PR build out of main workflow that is publishing to NuGet each CI
• Add env flags to remove unnecessary spew for CI
• Ignore changes to .git files

It may be preferable (at least as an option) to install the Tailwind CLI locally in the project's node_modules folder.

My understanding is that NPX would then always use that locally installed version.

This might help usage of the template in offline scenarios as, following the initial build (which would download and install the Tailwind CLI) there should be no need for subsequent builds to require an Internet connection.

Leverage the PackageReadmeFile to include the README in the package, which then provides a better experience on nuget.org and within other NuGet clients.

At the moment we're invoking the Tailwind CLI on every Debug build.

This is largely pointless because the first build creates wwwroot\css\app.css and thereafter there are only a few scenarios where we'd want to rebuild that file.

• When the version of Tailwind changes
• When we elect to run a Release build
• If we make changes to Styles\app.css

For any other Debug/Dev builds we're just doing unnecessary work (and slowing down the build).

The template currently allows for creating .NET 6 projects, would be great to be able to target .NET 5 and potentially earlier versions of .NET (Core) too.