Possible performance issue

[dylang]

It seems like we're requiring all sass files to be re-read and processed by sass every time this task runs.

When used during development with watch does this means every time a sass file is changed the entire collection needs to be re-read off the HD and re-processed by sass?

If so this seems like a potential performance hit for sites with a lot of sass code.

I'm very new to sass and don't know what the right solution is for this.

[shama]

There is a discussion on this over at gruntjs/grunt-contrib-watch#14
(at least its the latest of many discussions on this issue)

[sindresorhus]

I'm fully aware, I've mentioned it on several occasions, but it's not specific to this task. Almost every task could be sped up by only processing changed files. This is especially apparent in tasks like Sass or image minification.

For now, one thing you can do is to create separate watch targets for different parts of your app, if you have many different Sass pieces. That way only the files in each target will be processed when one is changed. Though this is only a temporary bandaid.

[tkellen]

Closing this for now. This definitely won't be solved at the sass task level. This is on our radar, but it's a long way out.