-
Notifications
You must be signed in to change notification settings - Fork 29.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
Make npm install work again with NPM 5 #30759
Conversation
… causing the wrong version of v8-profiler to be installed and the node-gyp build to fail.
…rors. Possibly due to a dependency chain mismatch pulling in an incompatible extract-zip version.
@ivanz, thanks for your PR! By analyzing the history of the files in this pull request, we identified @joaomoreno and @bpasero to be potential reviewers. |
Thanks! |
NPM5 support: #30134 |
I'm running npm 5.3.0 same error after your merge @joaomoreno
UPDATE: |
I am in holiday atm, but saw that the second change in this PR caused pains/breakage (sorry about that!), so the PR was reverted, which included change 1 for the electron build fix. Basically the version string in package.json doesn't match the shrinkwrap file, so the shrinkwrap doesn't get used and NPM installs the wrong v8-profiler package missing electron compatability patches. I won't be able to open a PR in the next week, but if someone were to just move the first commit into its own PR - that should do the trick I think. |
Two issues fixed:
I think there was a version string mismatch which was causing the mainstream
v8-profiler
to be installed instead of the vscode electron-compatible fork in the shrinkwrap. This was causing the node-gyp step for v8-profiler package to fail with a build errorOnce the above was fixed then the extract of some electron bits started failing. Updating the
yauzl
package used for unzipping stuff fixed that. I suspect something was happening under the hood that resulted in a version mismatch betweenextract-zip
andyauzl
. The future proof fix here will be to update to NPM5 package lock files I guess.Relates to #30134