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
fsevents installation crashes with "'MSVSProject' object has no attribute 'iteritems'" #661
Comments
Same for me. |
same here npm 3.1.2 / io.js v2.3.4 / osx 10.10.4 any fix, solution? |
+1 |
I've downgraded to npm 2.11.2 and the package was installed normally. |
I've the issue but can't go back to npm < 3.0 because I really need flattened node_modules folder feature of npm 3.0. |
I've gotten this error, but the modules worked fine anyways. Last time I specifically remember this happening is with webpack. Using 3.1.0 in Windows 8.1. Discussed in the fsevents repo in fsevents/fsevents#73. |
And NPM is fixing the errors for optional modules: npm/npm#8921 |
@rchanou I just came across that npm issue myself. It looks like that's the real culprit. |
Hey! Good news, this should be fixed in the just released |
Awesome news @iarna just tested the new release right now and worked like a charm! Many thanks! |
Thanks @iarna :) |
Hey, @iarna! I still have this problem with npm 3.5.0.
We are using shrinkwrap.json if it's important. |
If I delete shrinkwrap.json and node_modules folder then the problem goes away. But I get another warning
Not sure if the problem is solved because fsevents is updated after deleting shrinkwrap.json.. |
Help pls /
C:\work\f8app\node_modules\fsevents>if not defined npm_config_node_gyp (node "C:\Users\Alexei\AppData\Roaming\npm\node_m C:\work\f8app\node_modules\fsevents>if not defined npm_config_node_gyp (node "C:\Users\Alexei\AppData\Roaming\npm\node_m
npm ERR! fsevents@1.0.11 install: npm ERR! Please include the following file with any support request: |
+1 |
This is no longer an issue if you follow the install steps from node-gyp module readme file. Make sure you have the proper MSVS version installed, the correct env PATH set, and env vars set. Also update your Git version from the website, it solves a lot of issues. Make sure git is available from the CMD and only from Gitbash. The only problem might be where npm modules are very old and outdated. There nothing you can do for this, unless you start raising PRs to fix them. Also you can use |
Still doesn't work with npm@3.9.5 on Windows 10... :/
|
Ping, any update? |
@bpasero If fsevents is in optionalDependencies, I think it should Just Work(TM). Speaking with both my fsevents and node-gyp maintainer hats on. |
@bnoordhuis we use npm-shrinkwrap and so fsevents will be compiled even if it is a optional dependency. I think npm/npm#12698 is the root cause of that. |
Can someone fix this issue ASAP ! |
+1 same issue with npm 3.10.3 |
Happening for me as well on Windows 8.1 and npm version 3.10.9. Any updates on this? |
I'm getting this on Windows 7, npm 5.0.3. |
Same issue on Windows 10, npm 5.0.3 |
This is an npm bug, node-gyp fails to compile fsevents on Windows because it should only be installed on macOS. There is nothing node-gyp can do to fix it. @bpasero mentioned that npm/npm#12698 might be the cause of the bug, please see that issue, or raise/find a newer one on https://github.com/npm/npm/ if there's a new issue with npm5. |
Is there a work around @gibfahn ? |
Vote on npm/npm#16810 |
Possible workaround run |
still an issue, with latest npm
|
And again a problem with node-gyp 5.0.5 in this env:
Update: Upgrading to node-gyp 6.1.0 didn't help. It still uses node-gyp 5.0.5 This workaround worked for me, and maybe useful to others, too. |
Does the error message say |
The error message is:
Note that in the screenshot it says node-gyp 5.05. However, version 6.1.0 is installed globally.... Update: Meanwhile I cannot reproduce the problem anymore. I do not know what change made this work. I no longer need the workaround (locking fsevents to particular version) anymore either. |
@cclauss The error message says iteritems. Here are a bunch of screenshots. A list of globally installed packagesnpm installAfter setting node_gyp in
|
node-gyp is v3, not v7 |
Wow its 2021, I'm having this now, win10
|
|
Fascinating that Windows processes are trying to install the macOS-only https://www.npmjs.com/package/fsevents This is noted in the original post at the top of this issue. |
I had the same issue as @jamietre in npm/npm#8878. Looking at the stack trace, I'm pretty sure it's node-gyp that's encountering some sort of error while trying to install fsevents (a Mac OS X-specific module, from the looks of it). The error message seems generic enough to be a gyp-related one rather than an fsevents one though, so I'm filing it here.
The text was updated successfully, but these errors were encountered: