-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error with Node v6.0.0? #824
Comments
Problem seems to be in fsevents library (fsevents/fsevents#127) which is used by chokidar. |
+1 |
1 similar comment
+1 |
As a developer, every "+1" hit and leave, discourages me from actually wanting to do anything. It's the equivalent of saying "yeah! Just fix it!!!" whilst you make no contribution at all. At least olalonde identified that it's a problem with Chokidar. My guess? Bump the version dep. Send me a PR with a change to the |
@remy oh man, I feel for you. Sometimes, open source users can feel pretty entitled and forget that you don't owe them anything. Node v6 was just released and a lot of native modules are breaking due to a backwards incompatible change in the native API (nodejs/node#6277). I just reported this here as a heads up, best we can do right now is to wait for the upstream modules to get this fixed. PS: thanks for nodemon! |
Looks like the root cause is being tackled by this PR in fsevents. We just have to wait for both fsevents and chokidar releases. |
+1 |
Damn son, some people are funny. |
https://github.com/strongloop/fsevents/releases/tag/v1.0.12 has been released! 🎉 |
Yay, guess we can close this now. Just installed nodemon again and error is gone. Added node v6 to travis.yml #826 if it helps |
* 'master' of https://github.com/mgcrea/nodemon: chore(npm): bump chokidar and test against node@^6.0 (fixes #824)
* mgcrea-master: chore(npm): bump chokidar and test against node@^6.0 (fixes #824)
All appropriate deps bumped thanks to an external PR and live in 1.9.2. 💟💪 |
@remy |
@halt-hammerzeit beatch? |
@maban Yeah, it's like when sand gets in your eyes — it really makes you cry a lot. |
nodemon seems not works with node v6. |
I'm still seeing these errors on the latest version:
Update: this was another module in my Node app ( |
@vimniky this issue is closed now, can you open a new issue with specific details. My latest test with node@6 shows nodemon working, but I don't know the details of your particular problem. Same with @OliverJAsh - though this seems more like a specific thing with your project. Can you par it down to a single script to replicate the error (and raise separately). |
Reproduces in
|
I just installed Node v6.0.0 and getting a weird error when using nodemon.
The text was updated successfully, but these errors were encountered: