Open safetypins opened 6 years ago
Hi there - just ran into this issue myself after recently upgrading to sassc from sass.
After some additional digging it looks like this had been raised on another ticket with a solution that worked for me (removing .scss from any @import statements).
https://github.com/sass/sassc-rails/issues/55
Also found on stackoverflow: https://stackoverflow.com/questions/34801411/sassc-rails-assets-changes-not-being-compiled/34815948#34815948
Maybe this helps @safetypins ?
Thank you @jesseiqmi - I had the same reload issue in development and removing .scss
from the @import
statements did fix it for me.
I had the same issue, even application.scss
changes didn't update before restarting the Rails server.
Adding this to development.rb
fixed it for me:
config.assets.compress = false
I had the same issue, even
application.scss
changes didn't update before restarting the Rails server.Adding this to
development.rb
fixed it for me:config.assets.compress = false
That did the trick for me
I'm using the following configuration for my development environment:
But changes that I make in /app/assets/stylesheets/*.scss files are not visible until I delete the /tmp/cache/assets directory.
I know this is probably not a sassc-rails issue, but I didn't encounter this issue when I was using the regular sass-rails gem. Any idea how I can streamline my style development workflow? I started using sassc-rails for the inline mapping, but I think it might be faster for me to develop without them if I have to delete the assets directory for scss changes to be visible.