watching newly created files

Greetings!
When I start node-sass in recursive watching mode it works just fine with the exception that newly created files are not being watched.
For example, if I wach a directory and I add new styles.scss file, node-sass ignores this file, providing the process has already been started before.
Is it possible to change this behavior? Or do I just miss something?

I can also reproduce this on OS X Sierra with node-sass@4.5.0.
My command looks like this:

node-sass src/ -o src/ --watch --recursive

Adding src/wow.scss (and saving it multiple times) has no effect until I restart the watcher, at which point it works as intended for this file (but not for any new files).

I also tried removing the --recursive flag but it doesn’t seem to have any effect.

This is a know issue. I'll make a patch in the next release

…

On 12 Feb. 2017 11:24 am, "Dan Abramov" ***@***.***> wrote: I can also reproduce this on OS X Sierra with ***@***.*** My command looks like this: node-sass src/ -o src/ --watch --recursive Adding src/wow.scss (and saving it multiple times) has no effect until I restart the watcher, at which point it works as intended for this file (but not for any new files). — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1891 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAjZWLKioJ_rxpM7QIRE8D7Ty5njyS_Fks5rblEggaJpZM4L9BgX> .

Specifically the added event does not rebuild the watch graph so the watcher doesn't know the new file exists.

…

On 12 Feb. 2017 12:04 pm, "Michael Mifsud" ***@***.***> wrote: This is a know issue. I'll make a patch in the next release On 12 Feb. 2017 11:24 am, "Dan Abramov" ***@***.***> wrote: > I can also reproduce this on OS X Sierra with ***@***.*** > My command looks like this: > > node-sass src/ -o src/ --watch --recursive > > Adding src/wow.scss (and saving it multiple times) has no effect until I > restart the watcher, at which point it works as intended for this file (but > not for any new files). > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#1891 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAjZWLKioJ_rxpM7QIRE8D7Ty5njyS_Fks5rblEggaJpZM4L9BgX> > . >

Thanks for such a quick response!
👍

Watcher should track newly created files

I wonder if you could possibly reconsider #1369 at the same time? I believe it would improve consistency across the board.

With #1369 implemented - all files are guaranteed to be in a compiled state whether they already existed or were created while watching.
Without it - files that already exist are not compiled. Files that are created while watching are compiled. This seems inconsistent and fiddly to manage.

Thanks for your consideration.

Watcher should track newly created files

@xzyfer

@xzyfer Even more unfortunate, our existing .scss files, when edited, are no longer compiled into .css. So this is a wonderful fix if you're editing and using .css directly, but if you're using .scss compiled to .css it has the same issue as before and introduces a regression.

TO BE CLEAR and I should have said this before, we're using create-react-app and so if its configuration needs to change, we haven't yet done that.

This project was bootstrapped with [Create React App](https://github.…

@gaearon

This issue was closed but was not actually resolved. I'm running v4.9.4 on OSX 10.12.2 (Sierra) and the problem persists, exactly as described by @gaearon

node-sass-chokidar doesn't suffer from this issue, at least on my machine. From what I understand the only difference between the two is that nsc uses chokidar instead of Gaze to watch files, but I'm totally out of my depth here.

This issue was closed but was not actually resolved

Not resolved in july 2019 either (running Linux), but still 'Closed' on github unfortunately :(

I'm still having this problem, Oct 2019. Running Mac OS Mojave. Please think of reopen this

@mankinchi

@mankinchi can you build a simple repository with a script to demonstrate this?

Same problem, January 2020.

Same problem, February 2020. Any solution?

Having exactly the same issue. Using latest node-sass 14.4.1 (July 2020) and Windows 8.1 machine. Still no solution?
Here is how my command looks like: node-sass sass/main.scss css/style.css -w --recursive

update: ended up installing node-sass-chokidar and now everything works as it should

@t-kowalewski

Also having this exact issue. Thanks @t-kowalewski just swapped to node-sass-chokidar and it's now working fine!

Same here with Node 12.18.3 and node-sass 4.14.1

issue still exists :(

Node 21 and node-sass 9.0

Navigation Menu

Repository navigation

watching newly created files #1891

17 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

watching newly created files #1891

Description

Activity

gaearon commented on Feb 12, 2017

xzyfer commented on Feb 12, 2017

xzyfer commented on Feb 12, 2017

gaearon commented on Feb 12, 2017

NigeNigeNige commented on Feb 28, 2017

17 remaining items

adamdonahue commented on Jul 30, 2017

kylebebak commented on Nov 1, 2018

Friksel commented on Jul 9, 2019

mankinchi commented on Oct 18, 2019

saper commented on Oct 18, 2019

baglio commented on Jan 8, 2020

diegoulloao commented on Feb 11, 2020

t-kowalewski commented on Jul 22, 2020

Mofunkles commented on Oct 20, 2020

bago2k4 commented on Nov 16, 2020

pavelee commented on Oct 26, 2023

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions