Inconsistent behavior when using directory input with --watch and without --watch

[lephuongbg]

Current behavior

• When using directory input without --watch, all .scss files will be compiled and normal css files won't be compiled.
• When using directory input with --watch, when any css file changed, they will be compiled.

Suggested behavior

When using directory input with --watch, we should watch .scss files only.

---

• NPM version (npm -v): 3.10.3
• Node version (node -v): 6.3.1
• node-sass version (node -p "require('node-sass').info"): 3.10.1

[wuzhouyang]

resolved?

[xzyfer]

if the issue still open it's not resolved.

[nschonni]

Only watching SASS/SCSS files appears to be in the current code https://github.com/sass/node-sass/blob/master/bin/node-sass#L135

[nschonni]

Nevermind, it looks like the watcher does look for css here https://github.com/sass/node-sass/blob/master/bin/node-sass#L243

[xzyfer]

This looks like a bug I introduced in #1078. We should not be watching .css files.

[kibbled]

Is there a workaround for this bug?

[eugeneglova]

hey @xzyfer could you just make these extensions to be configurable so I can remove css from that lis as a workaround for this issue. Should I create PR for that?

[xzyfer]

They cannot be configured. They live in LibSass. The decisions has been made to keep the current behaviour until Sass 4's module system is ready. Removing this now will break lots of people's code.

[kibbled]

This bug sort of causes infinite compiles to happen when you watch a directory because after SCSS files compile to CSS, the watcher detects changes and recompiles the CSS which starts a vicious cycle Perhaps a recommendation in the documentation for using a different directory for your CSS files from your SCSS files since it's unusable in the current form.

[RoyTinker]

Looks like the best workaround is to use node-sass-chokidar.

[xzyfer]

So I think the reasonable workaround for this is for node-sass to not treat .css as entry points.

We still need to watch .css files, this is unavoidable with breaking things for users, but we should only trigger compilations for CSS files that are imported by scss files.

This is a patch I think wen can ship before the 5.0 bump and should fix the majority of issues around watching css files.

[RoyTinker]

@xzyfer is this still planned for a pre-5.0 patch?