-
Notifications
You must be signed in to change notification settings - Fork 118
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
NPM 3 issue #73
Comments
There's no need to build fsevents on windows. |
Besides, I don't think this is related to fsevents in the first place. The build error is this:
And that comes from gyp / node-gyp. Make sure you have python 2 installed, not 3. |
everything that uses fsevents fails
|
@es128 Ah didn't know what. I don't think it's npm related anyway because I remember it failing before I updated. Wish packages could skip it or not have it throw confusing errors on windows |
That should be the case. Chokidar lists fsevents as an There's a chance in your case that you can't get that far because your build chain is broken for any native extensions via npm and it doesn't handle that case as well. Might be good to report the condition to the npm issue tracker. |
This is a bug on NPM, they are working on it: npm/npm#8921 |
This bug is particularly annoying on Windows because it seems to be the first (most depended upon maybe?) native module that always bombs. It used to be socket.io and now they've removed the native dependency so its this. Its more frustrating than socket.io because Windows users obviously don't want this package. I agree this is an npm bug but it would be cool if there was a way to shim this for Windows, although I'm not sure if its even possible to make gyp skip the native build. I use Mac and Windows, and avoid native modules due to the stress on Windows. I will say that most the Windows issues are Windows issues (at work, I can't install C++ redistributables without wiping my machine, and at home Visual Studio is failing to install due to a bitshift error in the registry). The future of native modules is pretty brittle with gyp dying, ninja migration not a priority, and no simple native build tool on Windows. This likely was not the best place to post this, but this is the module that shows up the most. |
They just fixed it in npm |
@giggio yep.. was posted during the writing of my post. 👍 |
The text was updated successfully, but these errors were encountered: