npm ERR! code Z_BUF_ERROR when install
In my server(CentOS 7.2) I install the dependencies:
npm install
But I get bellow error:
npm ERR! code Z_BUF_ERROR
npm ERR! errno -5
npm ERR! unexpected end of file
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-02-11T21_03_20_261Z-debug.log
in the /root/.npm/_logs/2018-02-11T21_03_20_261Z-debug.log, the info is bellow:
10234 verbose bundle EBUNDLEOVERRIDE: Replacing [email protected]'s bundled version of readable-stream with [email protected].
10235 verbose unlock done using /root/.npm/_locks/staging-ace74a3b0cf47932.lock for /home/ubuntu/source_code_web/vue_admin_site/node_modules/.staging
10236 warn The package iview is included as both a dev and production dependency.
10237 warn [email protected] had bundled packages that do not match the required version(s). They have been replaced with non-bundled versions.
10238 verbose type OperationalError
10239 verbose stack Error: unexpected end of file
10239 verbose stack at Gunzip.zlibOnError (zlib.js:152:15)
10240 verbose cwd /home/ubuntu/source_code_web/vue_admin_site
10241 verbose Linux 3.10.0-327.el7.x86_64
10242 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
10243 verbose node v8.4.0
10244 verbose npm v5.3.0
10245 error code Z_BUF_ERROR
10246 error errno -5
10247 error unexpected end of file
10248 verbose exit [ -5, true ]
I tried use：
npm cache clean
to clean the npm, but fails:
npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead.
npm ERR!
npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-02-11T21_13_51_943Z-debug.log
Solution 1:
Try cleaning the cache with the command npm cache clean --force and retry your npm install.
Solution 2:
- "npm cache clean --force"
- "npm cache verify"
following steps helped me!! :-)
if problem still persist : "npm i npm"
Solution 3:
In the end, I delete the node_modules:
rm -rf node_modules
and deleted the package-lock.json,
then re-install:
npm install
It works for me.
Solution 4:
As suggested in npm GitHub
Node 8.9.0+ (and 9+) fix an issue where streams are terminated early in some scenarios. If you're getting this error upgrade to 8.9.
So you can just try to update your node and npm