search

jlitola / play-sass

Sass asset handling for Play Framework 2.0 *DEPRECATED*
MIT License
90 stars 28 forks source link

Plugin won't recompile changes to the .scss #11

Closed monzonj closed 10 years ago

monzonj commented 11 years ago

On windows, I managed to make the plugin work.

However if I start the play server (run) , and after i make any change to the scss, after refreshing the page the changes are not taken.

I have to stop sbt, delete the target and .sass-cache folder and restart sbt. Only then will the plugin recompile the styles.

This is very cumbersome and it is impossible to be any productive like this, have you guys experienced the same issue?

monzonj commented 11 years ago

I would like to elaborate some more on my issue.

It seems it is not a problem related to this plugin but to play in general. If you have a resource say 'styles.scss' that imports another file '_substyles.scss'. Changes to the second won't be recompilied unless you introduce changes to the main file as well

Weird.

mcveat commented 11 years ago

And I will add that scss resources are recompiled if when you change included files that are in the same directory as main file

ianatha commented 11 years ago

I'm having the same issue.

A workaround seems to be adding resourceGenerators in Compile <+= SassPlugin.sassWatcher to your project's settings.

jlitola commented 10 years ago

I just tested this in Play 2.2 and play-sass 0.3.0, and the main file is recompiled if I changed imported file either in same directory or in subdirectory. If this still is issue, please re-open the issue and provide test project showing this behaviour.

geometricpanda commented 10 years ago

We're getting the same issue on the latest version, it appears that imported SCSS resources aren't always being watched.

Also we're noticing that imports within imports don't watch for recompile. As a temporary workaround we're having to modify our main SCSS file to force a recompile.

bigjason commented 10 years ago

Anyone have a solution for this? We are having the same problem with updates to partials not triggering a recompile.

geometricpanda commented 10 years ago

As a workaround you can make minor changes to your primary style sheet, run SCSS compiler or the method I found most useful was to use the Codekit compiler and compile it to my target directory.

Sent from my iPhone

On 6 Dec 2013, at 00:30, Jason Webb notifications@github.com wrote:

Anyone have a solution for this? We are having the same problem with updates to partials not triggering a recompile.

— Reply to this email directly or view it on GitHub.

kflorence commented 10 years ago

This is still a problem for us as well.

freiguy1 commented 9 years ago

I'm having the same issue. @JimDrury 's change isn't terribly favorable for my front end dev, so i'm determined to figure it out! Tonight I'll try adding incrementalAssetsCompilation := true due to this comment in the readme from wayback:

0.1.1 [2012-08-10] Dependency tracking for imported files. Should behave correctly with incrementalAssetsCompilation := true. Changed to use play 2.0.3, sbt 0.11.3.

Perhaps this is what everyone's missing?