Tracking changes on multiple files, not only application.css about propshaft HOT 7 CLOSED

1 - Which css gem are you using: cssbundling-rails, dart-sass or tailwind-rails?

2 - Do you have a process running to watch the files and recompile when changing?

3 - Do changes in application.css work at least?

from propshaft.

1 - Which css gem are you using: cssbundling-rails, dart-sass or tailwind-rails?

2 - Do you have a process running to watch the files and recompile when changing?

3 - Do changes in application.css work at least?

1 - tailwindcss-rails
2 - what do you mean? like bin/dev?
3 - yeah, changes copiles of course in this file, 'cause I attached it to application.html.erb in stylesheets_pack_tag, even if I attach file buttons.css (I mean by tag stylesheets_pack_tag) changes tracks too

from propshaft.

Yes, bin/dev. The tailwindcss-rails creates a Procfile that includes the watcher process:

web: bin/rails server -p 3000
css: bin/rails tailwindcss:watch

So, the usual "flow" is:
1 - You change app/assets/stylesheets/application.tailwind.css
2 - The watcher process noticed the changes, recompiles and places the file in app/assets/builds/tailwind.css
3 - Propshafts notices that the file it was tracking (app/assets/builds/tailwind.css) changed, so it reloads that file
4 - The changes become visible on the next page reload.

So, what I think is happening is that when you change the buttons.css file, instead of the application.tailwind.css file, the tailwind watcher is not noticing the change, and thus not recompiling.

Could you please test the following?
1 - Stop ./bin/dev
2 - Delete app/assets/builds/tailwind.css
3 - Run ./bin/dev
4 - Check app/assets/builds/tailwind.css exists
5 - Change button.css
6 - Check if the change is reflected in app/assets/builds/tailwind.css.

Is the answer to 6 is "No", then this is a problem in the tailwind gem and it's better if we move this discussion there.

from propshaft.

Yes, bin/dev. The tailwindcss-rails creates a Procfile that includes the watcher process:

web: bin/rails server -p 3000
css: bin/rails tailwindcss:watch

So, the usual "flow" is: 1 - You change app/assets/stylesheets/application.tailwind.css 2 - The watcher process noticed the changes, recompiles and places the file in app/assets/builds/tailwind.css 3 - Propshafts notices that the file it was tracking (app/assets/builds/tailwind.css) changed, so it reloads that file 4 - The changes become visible on the next page reload.

So, what I think is happening is that when you change the buttons.css file, instead of the application.tailwind.css file, the tailwind watcher is not noticing the change, and thus not recompiling.

Could you please test the following? 1 - Stop ./bin/dev 2 - Delete app/assets/builds/tailwind.css 3 - Run ./bin/dev 4 - Check app/assets/builds/tailwind.css exists 5 - Change button.css 6 - Check if the change is reflected in app/assets/builds/tailwind.css.

Is the answer to 6 is "No", then this is a problem in the tailwind gem and it's better if we move this discussion there.

answer to 6 is "No" for my bad(, it's not to change this file, it's even just not load the file to the site

from propshaft.

@loqimean Do you think you can provide me with a minimal project that demonstrates the problem? I'll debug it and figure out where the problem is.

from propshaft.

@loqimean Do you think you can provide me with a minimal project that demonstrates the problem? I'll debug it and figure out where the problem is.

okay, I will tag you when it's will be done

from propshaft.

Reopen when you have a reproducible setup.

from propshaft.