Purge also purges other stylesheets about tailwindcss-rails HOT 6 CLOSED

Hmm, yeah, that's a good issue. Probably need some way for the compressor to only apply to certain files. I'll have a look at that. And also, we need to document how to include the engine views to consider those – because that might well be relevant for Tailwind too, if you use that in your engines.

from tailwindcss-rails.

👋, haven't used Administrate but I'm guessing it's a Rails::Engine, so those views aren't considered, so the compressor would need to be told to look at those view files via something like:

config.assets.css_compressor = Tailwindcss::Compressor.new(files_with_class_names: Rails.root.glob("some/engine/root/**/*.*"))

(I don't know where to find the engine root though, depends on the gem install.)

But seems tailwindcss-rails should be Rails::Engine aware and the default app/views and app/helpers directories shouldn't be tied to just Rails.root necessarily. Can't remember how Rails::Engines automatically add their views to the main Rails app, but when we find that, I think we can reuse that to siphon extra locations to look.

from tailwindcss-rails.

Yeah, I think it's a good solution to make et engine aware. Just as a side note: There is stuff in the administrate.css file after purge because I have generated some of the Administrate views in the app/views folder.

I will go hunting for the path to the Administrate views :)

from tailwindcss-rails.

We've added Tailwind to our Rails engine (without webpacker) by compiling a custom build using npx that gets imported by Sprockets. It'd be great if instead of using npx to purge unnecessary classes, we could use this Purger to target our Tailwind build specifically (and skip the main app's stylesheets). I believe (as discussed in #1) it's better to do this in a separate gem though.

from tailwindcss-rails.

Hmm, yeah, that's a good issue. Probably need some way for the compressor to only apply to certain files. I'll have a look at that. And also, we need to document how to include the engine views to consider those – because that might well be relevant for Tailwind too, if you use that in your engines.

I think a good start would be to have an option to only purge Tailwind as it's already a separate file, which would make it less intrusive.

I am also a big fan of a general purger gem.

from tailwindcss-rails.

The fix works great, thanks 🥰

from tailwindcss-rails.