Unable to install webpack because of @webassemblyjs and @xtuc depedencies
dprosper opened this issue · comments
Please refer to this issue: webpack/webpack#8159 for more details.
Are you using a npm proxy or cache?
no proxy, cache (not really sure?). Interestingly on the exact same network it works on my Mac. Not on the PC.
I looked up the options for npm cache, I ended up running this command:
npm cache clean --force
however, that did not make a difference. after it completed the same error when trying to add webpack.
here is a npm log, if that helps any....
Seems that the issue is on your side.
seriously ?? any hints, why do you believe that to be the case? all other NPM pacakages are installed without any issues...
You are the only one that reported this issue, and on my side it works fine. I can't much more?
just wanted to jump in and say i just experienced this today although it was fine yesterday. Im having issues with xtuc/ieee754, webassembly doesn't seem to find the module
Edit: went and checked the package, weirdly it was only containing a package.json. I ran a simple npm i of the package and it worked again. Weird behavior though.
I am running into this as well.
Ok, @adriano515 @fzxt are you a npm proxy or cache?
I already reached out npm for a similar issue recently, I can ping them again for this one.
@xtuc I resolved this by commenting out all contents in my npmrc. It had reference to a proxy.
im using cache
I also ran into this issue.
As others have noticed, it appears to be related to the contents of the .npmrc file...
- Commenting out the contents of my .npmrc
- Running yarn install
- readding .npmrc contents
... worked for me
Same issue here. The strange thing is that it works on my local computer, but not on the CI pipeline!
Can't install any of this packages: @webassemblyjs/ast @webassemblyjs/helper-module-context @webassemblyjs/wasm-edit @webassemblyjs/wasm-parser npm throws this errors
/$ npm i --save @webassemblyjs/ast
npm ERR! code E401
npm ERR! 401 Unauthorized: @webassemblyjs/ast@latest
npm ERR! A complete log of this run can be found in:
npm ERR! ../.npm/_logs/2018-11-28T18_19_22_557Z-debug.log
/$ npm i --save @webassemblyjs/helper-module-context
npm ERR! code E401
npm ERR! 401 Unauthorized: @webassemblyjs/helper-module-context@latest
npm ERR! A complete log of this run can be found in:
npm ERR! ../.npm/_logs/2018-11-28T18_19_37_770Z-debug.log
/$ npm i --save @webassemblyjs/wasm-edit
npm ERR! code E401
npm ERR! 401 Unauthorized: @webassemblyjs/wasm-edit@latest
npm ERR! A complete log of this run can be found in:
npm ERR! ../.npm/_logs/2018-11-28T18_20_02_709Z-debug.log
/$ npm i --save @webassemblyjs/wasm-parser
npm ERR! code E401
npm ERR! 401 Unauthorized: @webassemblyjs/wasm-parser@latest
npm ERR! A complete log of this run can be found in:
npm ERR! ../.npm/_logs/2018-11-28T18_20_17_690Z-debug.log
It may be the case of a private scope on npm?
Same issue!
This are the yarn errors this packages: @webassemblyjs/ast @webassemblyjs/helper-module-context @webassemblyjs/wasm-edit @webassemblyjs/wasm-parser
/$ yarn add @webassemblyjs/ast -d
yarn add v1.3.2
info No lockfile found.
[1/4] 🔍 Resolving packages...
error Couldn't find package "@webassemblyjs/ast" on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
/$ yarn add @webassemblyjs/helper-module-context -d
yarn add v1.3.2
info No lockfile found.
[1/4] 🔍 Resolving packages...
error Couldn't find package "@webassemblyjs/helper-module-context" on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
/$ yarn add @webassemblyjs/wasm-edit -d
yarn add v1.3.2
info No lockfile found.
[1/4] 🔍 Resolving packages...
error Couldn't find package "@webassemblyjs/wasm-edit" on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
/$ yarn add @webassemblyjs/wasm-parser -d
yarn add v1.3.2
info No lockfile found.
[1/4] 🔍 Resolving packages...
error Couldn't find package "@webassemblyjs/wasm-parser" on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
The issue maybe on the npm scope of the organization or the packages...
This is an npm tokens issue.
Check webpack/webpack#8434 (comment)
I'm closing this issue for now since there's no activity, feel free to comment here and I will re-open it.
@xtuc , this definitely seems to be a bigger npm issue. A few other npm packages are experiencing this as well.
Need to get more traction on this issue here - https://npm.community/t/always-reproducible-maximum-call-stack-size-exceeded-npm-install-error/1645/
I just encountered this issue, and I don't even have a .npmrc.
Note that when I visit:
https://registry.npmjs.org/@xtuc%2flong
It says: Not found
Same issue here :-/
Trouble with registry. It's a reason to have additional registry.
Fixed for me by running npm login on the command-line.
There's an ongoing npm incident https://status.npmjs.org/incidents/cksjqc1w11v5.
Same issue here :-(
Same issue. https://registry.npmjs.org/@xtuc%2flong returns 404.
This is due to an ongoing npm incident https://status.npmjs.org/incidents/cksjqc1w11v5.