-
Notifications
You must be signed in to change notification settings - Fork 188
Assets are never re-compiled #7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Just so I understand, based on https://github.com/rails/tailwindcss-rails/blob/main/lib/tailwindcss/engine.rb The tailwind file is registered, but that file is never going to change, right? I assume Sprockets will never trigger a new compile if the source files don't change... is there a way to tell Sprockets that the compressor is going to produce different output this time, so it should re-compile even if the inputs are the same? |
Yeah, we should document this limitation at the moment. Feel free to look into whether there's a way to tell sprockets that the compressor thinks its time for a rebundle, even if the source didn't change. |
Sprockets has a |
Oh, that's a great idea. Let's give that a try 👍 |
PR #12 raised, uses the |
Documented need for clobber in a2abc42. |
The way I'm working around this now is to disable the asset cache using the instructions in https://guides.rubyonrails.org/v6.1/asset_pipeline.html#assets-cache-store I'd suggest documenting this as the recommended approach, it's the only way I can see that handles all the edge cases. It also works to automatically fix the Heroku build even if it was deployed without switching off the cache. |
Made this the default in 2097fc4. |
There seems to be a caching issue happening—
assets:precompile
does nothing even if new classes are used and purging needs to happen again. I have to runassets:clobber
first to force a full re-compile.The text was updated successfully, but these errors were encountered: