Have you seen this new experimental feature ...

[hugh-maaskant]

Hi,

I recently learned about this new (still experimental) build feature for npm (and the like) builds.

Wanted to draw your attention to it as it may be overlapping / be of use t0 your solution (that I adopted)

https://devblogs.microsoft.com/dotnet/build-client-web-assets-for-your-razor-class-library/

Cheers

[McNerdius]

So, i looked the blog post over a few times. My initial take was "what problem is this solving" (that can't be followed by MSBuild itself). Another quick skim before bed yielded "integrating a client web asset build pipeline into the build process [...] can be challenging." Fortunately we don't need webpack or yarn type stuff and only one file to handle, so... not terribly challenging, lol.

Turns out all this package is, is a .targets file: Microsoft.AspNetCore.ClientAssets.targets. Literally the only thing in the package ! I guess for bigger projects dealing with a legitimate pipeline, a sort of all-purpose approach could be suitable, but the only thing i've ever had to change when using tailwindcss.targets has been the number of dots for Inputs/Outputs on the NpmInstallCheck target to check in current or parent directory, depending on my solution setup.

Anyhoo, i know not everyone is actively avoiding JS frameworks/build tools like i am - so i'll be sure to mention this in the upcoming content rehash of tailblazor.dev. Thanks for the heads up !