You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I enabled sass for my stylesheets in _config.yml, and I started my server with --auto option, but every time I change a .css.scss file, I need to save it twice in order to see my css updated on the static copy even if webrick detected a change. Not a real problem but it's really an annoying behaviour.
Don't know if this issue could be related to this plugin, but there's a way to overcome the problem and avoid to save the sass file one more time?
Thank you
The text was updated successfully, but these errors were encountered:
Hm. Sometimes it works on my laptop as expected, sometimes I get described bug. o_O Seems like under some circumstances DirectoryWatcher starts ignoring changes to _assets.
DirectoryWatcher was not the cause. It was the bug in the AssetFile equality comparison and eventual caching. So obsolete assets were kept in the cache while new asset versions were added into the stack that was leading into race conditions during compilation. Fixed in v0.3.7
I enabled sass for my stylesheets in
_config.yml
, and I started my server with--auto
option, but every time I change a.css.scss
file, I need to save it twice in order to see my css updated on the static copy even if webrick detected a change. Not a real problem but it's really an annoying behaviour.Don't know if this issue could be related to this plugin, but there's a way to overcome the problem and avoid to save the sass file one more time?
Thank you
The text was updated successfully, but these errors were encountered: