Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

执行npm install --save react npm install --save react-dom npm install --save-dev webpack  的时候遇到以下错误 #15857

Closed
wuxia510 opened this issue Feb 24, 2017 · 2 comments

Comments

@wuxia510
Copy link

Is this ok? (yes) yes

D:\myreact>npm install --save react
myreact@1.0.0 D:\myreact
`-- react@15.4.2

npm WARN myreact@1.0.0 No repository field.

D:\myreact>npm install --save react-dom
myreact@1.0.0 D:\myreact
`-- react-dom@15.4.2

npm WARN myreact@1.0.0 No repository field.

D:\myreact>npm install --save-dev webpack
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Fil
node_modules\npm\bin\npm-cli.js" "install" "--save-dev" "webpack"
npm ERR! node v6.10.0
npm ERR! npm v3.10.10

npm ERR! shasum check failed for C:\Users\ADMINI~1\AppData\Local\Tem
e496a53\registry.npmjs.org\pako-\pako-0.2.9.tgz
npm ERR! Expected: f3f7522f4ef782348da8161bad9ecfd51bf83a75
npm ERR! Actual: d4e22a9f107defe26c24f8888dba314887bf91f8
npm ERR! From: https://registry.npmjs.org/pako/-/pako-0.2.9.tgz
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues

@wuxia510 wuxia510 changed the title 执行npm install --save react npm install --save react-dom npm install --save-dev webpack  的时候博爱一下错误 执行npm install --save react npm install --save react-dom npm install --save-dev webpack  的时候遇到一下错误 Feb 24, 2017
@wuxia510 wuxia510 changed the title 执行npm install --save react npm install --save react-dom npm install --save-dev webpack  的时候遇到一下错误 执行npm install --save react npm install --save react-dom npm install --save-dev webpack  的时候遇到以下错误 Feb 24, 2017
@legodude17
Copy link
Contributor

Hello! This is a duplicate of #14626. Try updating to the latest version of npm, as it was fixed there.

@npm-robot
Copy link

We're closing this issue as it has gone seven days without activity and without being labeled. If we haven't even labeled in issue in seven days then we're unlikely to ever read it.

If you are still experiencing the issue that led to you opening this or this is a feature request you're still interested in then we encourage you to open a new issue. If this was a support issue, you may be better served by joining package.communty and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants
@legodude17 @wuxia510 @npm-robot and others