.sass-cache grows infinitely

[DougPuchalski]

Using ember-cli, I've noticed that .sass-cache is placed in the root directory of the project. Perhaps due to the nature of how trees get build, many versions are created and this grows quite huge over time.

I see that neither broccoli-sass nor node-sass doesn't pass cache_location to the SASS compiler. The SASS docs indicate that some frameworks set this path to a /tmp directory which seems appropriate. Any opinion on where this concern would belong, either here or in ember-cli?

[simonexmachina]

I've seen this directory before, but it doesn't exist in any of my projects that use ember-cli or broccoli-sass (or ember-cli-sass). I suspect that it's coming from somewhere else - your editor maybe?

[DougPuchalski]

Hmm, per sass docs caching is enabled by default, I don't see anything disabling it (via cache: false) either here nor in node-sass.

[simonexmachina]

Maybe try running ember new and ember serve, load the page in the browser without running anything else on the project (eg. editors etc) and see if that folder's created. Because it's not happening for any of us here. One of the other developers here says that it's created by the sass executable, which isn't used by broccoli-sass (it uses libsass).

[DougPuchalski]

@aexmachina That would explain it, broccoli-ruby-sass in another branch.