search

MustansirZia / next-express-bootstrap-boilerplate

:zap: JavaScript boilerplate for a full stack app built using React.js, Next.js, Express.js, react-bootstrap, SCSS and full SSR with eslint.
MIT License
112 stars 20 forks source link

sudo npm i -g next-express-bootstrap-boilerplate does not work #7

Closed H3RSKO closed 5 years ago

H3RSKO commented 5 years ago

I get this error why trying to run: sudo npm i -g next-express-bootstrap-boilerplate

Unhandled rejection Error: EISDIR: illegal operation on a directory, open '/Users/user/.npm/_cacache/content-v2/sha512/34/cd'

npm ERR! cb() never called!

log: 0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', 1 verbose cli '/usr/local/bin/npm', 1 verbose cli 'i', 1 verbose cli '-g', 1 verbose cli 'next-express-bootstrap-boilerplate' ] 2 info using npm@6.7.0 3 info using node@v8.12.0 4 verbose npm-session c117a29c64dd2f85 5 silly install loadCurrentTree 6 silly install readGlobalPackageData 7 timing npm Completed in 1240ms 8 error cb() never called!

MustansirZia commented 5 years ago

I'm not so sure if this has something to do with the package itself. Try the following commands first to clean your npm cache.

sudo npm cache verify

H3RSKO commented 5 years ago

Didn't help:

sudo npm cache verify gives me:

Cache verified and compressed (~/.npm/_cacache):
Content verified: 3978 (122672040 bytes)
Content garbage-collected: 1422 (66270254 bytes)
Index entries: 6242
Finished in 10.065s

But then when I ran sudo npm i -g next-express-bootstrap-boilerplate again I got the same error as before.

MustansirZia commented 5 years ago

Try clearing the entire cache now, please. sudo npm cache clear.

H3RSKO commented 5 years ago

I think I'm running into this problem which seems pretty common: https://npm.community/t/crash-npm-err-cb-never-called/858/10

MustansirZia commented 5 years ago

@H3RSKO close the issue if you're satisfied.

MustansirZia commented 5 years ago

Closing due inactivity.