npm 错误!尝试获取 http://registry.npmjs.org/accepts 时响应正文无效:sha 完整性验证失败

ant*_*oos 11 npm angular-cli

npm 错误!尝试获取http://registry.npmjs.org/accepts 时响应正文无效:<某些我可能不应该共享的密钥> 的完整性验证失败

尝试安装 angular cli 和 express 时,我在 RPI4 (raspbian) 上收到此错误。我按照另一个线程中的建议降级到 npm 6.13.7,但没有成功。

小智 25

尝试清除缓存并重新安装

npm 缓存清除 --force

安装


it3*_*3xl 14

npm cache verify
npm install

以上对我有帮助。请参阅不带密钥的命令
输出中的详细信息。 就我而言是npm cache clean--force

$ npm cache clean
npm ERR! As of npm@5, the npm cache self-heals from corruption issues
npm ERR! by treating integrity mismatches as cache misses.  As a result,
npm ERR! data extracted from the cache is guaranteed to be valid.  If you
npm ERR! want to make sure everything is consistent, use `npm cache verify`
npm ERR! instead.  Deleting the cache can only make npm go slower, and is
npm ERR! not likely to correct any problems you may be encountering!
npm ERR! 
npm ERR! On the other hand, if you're debugging an issue with the installer,
npm ERR! or race conditions that depend on the timing of writing to an empty
npm ERR! cache, you can use `npm install --cache /tmp/empty-cache` to use a
npm ERR! temporary cache instead of nuking the actual one.
npm ERR! 
npm ERR! If you're sure you want to delete the entire cache, rerun this command
npm ERR! with --force.
Run Code Online (Sandbox Code Playgroud)