-
-
Notifications
You must be signed in to change notification settings - Fork 189
Watching files with multiple imports is broken #123
Comments
I am not sure on what you are saying since right after that you say that commenting an import is making a change. Do you expect to get a verbose ouput that is saying that index.css is watched in the first place ? $ cssnext --watch -v index.css bundle.css
[11:52:27] Output written /Users/clemens/Projects/cssnext-bug/bundle.css
[11:52:40] Watching /Users/clemens/Projects/cssnext-bug/index.css And then when you comment an import you get $ cssnext --watch -v index.css bundle.css
[11:52:27] Output written /Users/clemens/Projects/cssnext-bug/bundle.css
[11:52:40] Watching /Users/clemens/Projects/cssnext-bug/index.css
[11:52:47] Output written /Users/clemens/Projects/cssnext-bug/bundle.css Is that what you would expect ? |
No, the first one (with both imports) doesn't pick up any changes at all. For the second one I restarted One import === changes get detected and recompiled. |
Ok I will take a deeper look then, cause "it works for me™" on one project. Thanks for reporting ! |
The weird thing is: it used to work for me too :D then I reinstalled all my modules from scratch... Taking a look at the code: |
watcher.on("ready") doesn't fire for multiple imports (why? I don't know!), we want to listen to changes regardless. should fix MoOx#123
hmmm i think i'm seeing the same issue... |
Also seeing this. |
Looks like a chokidar bug paulmillr/chokidar#288 (comment) |
I will release this fix tomorrow morning (in 8 hours). Should be better now. Sorry for the delay guys. |
Thank you, Maxime 🎉 |
Hey,
it seems as if files with multiple imports don't get watched properly.
index.css
one.css
two.css
running cssnext does compile the files correctly, but doesn't watch
commenting out one
@import
yields the expected result:OSX 10.10.3
cssnext:
1.4.0
iojs:
1.8.1
Thank you! :)
The text was updated successfully, but these errors were encountered: