tailwind v4 changes

[8de2fdb0]

Tailwind v4 doesn't have a config anymore, it is possible to define a @config directive in the css file but that is not really intended to be used like that anymore.

The file detection works now different, it just searches all files as far as I can see so setting --cwd to something like src/ or crates/my_crate becomes more important. I have got from 54s to 2ms just by setting --cwd and preventing tailwindcss scanning my target folder.

I guess adding external tools into a rust bin is a moving target, it is nice to don't have to manage a build tool but using something like cargo make has the benefit of more flexibility when stuff changes.

[mondeja]

The file detection works now different, it just searches all files as far as I can see so setting --cwd to something like src/ or crates/my_crate becomes more important. I have got from 54s to 2ms just by setting --cwd and preventing tailwindcss scanning my target folder.

You can put your target/ folder inside .gitignore and will not be checked. See https://tailwindcss.com/docs/detecting-classes-in-source-files#which-files-are-scanned

[baodrate]

alternatively, if you don't want to include those paths in your .gitignore, you can use .ignore (same syntax)

https://github.com/tailwindlabs/tailwindcss/blob/aa859314d9cd0a54f1914051c2a400d81bd7bed2/crates/ignore/src/walk.rs#L441-L443

[8de2fdb0]

Yes thanks that are good suggestions, I ended up moving all my leptos workflow to cargo-make it is just much more flexible. And there was anyway a bit too much magic when using cargo leptos, now i can easily adopt things quickly.

[baodrate]

@8de2fdb0 that's a good idea, I was thinking about doing similarly, but hadn't yet investigated how difficult that would be. do you have your setup somewhere you can share?

[8de2fdb0]

this gist is a workspace having separate wasm32/backend crates

the watch target isn't implementd

https://gist.github.com/8de2fdb0/5ecc0d23d347e2b5cee0858ec2d9b90e/edit