cb() never called while installing yargs

I wanted to install yargs. npm version 6.9.0
npm install yargs --save

Got this error.
npm ERR! cb() never called!

    npm ERR! This is an error with npm itself. Please report this error at:
    npm ERR!     <https://npm.community>

Here’s the log.

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'install',
1 verbose cli   'yargs',
1 verbose cli   '--save' ]
2 info using npm@6.9.0
3 info using node@v8.10.0
4 verbose npm-session 32fa8efe4c34db29
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 http fetch GET 304 https://registry.npmjs.org/yargs 687ms (from cache)
8 silly pacote tag manifest for yargs@latest fetched in 700ms
9 timing stage:loadCurrentTree Completed in 748ms
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 timing stage:loadIdealTree:cloneCurrentTree Completed in 1ms
13 silly install loadShrinkwrap
14 timing stage:loadIdealTree:loadShrinkwrap Completed in 4ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule yargs@13.2.4 checking installable status
17 http fetch GET 304 https://registry.npmjs.org/os-locale 325ms (from cache)
18 silly pacote range manifest for os-locale@^3.1.0 fetched in 333ms
19 silly resolveWithNewModule os-locale@3.1.0 checking installable status
20 http fetch GET 304 https://registry.npmjs.org/y18n 332ms (from cache)
21 silly pacote range manifest for y18n@^4.0.0 fetched in 334ms
22 silly resolveWithNewModule y18n@4.0.0 checking installable status
23 http fetch GET 304 https://registry.npmjs.org/require-directory 345ms (from cache)
24 http fetch GET 304 https://registry.npmjs.org/set-blocking 342ms (from cache)
25 http fetch GET 304 https://registry.npmjs.org/require-main-filename 347ms (from cache)
26 silly pacote range manifest for require-directory@^2.1.1 fetched in 349ms
27 silly resolveWithNewModule require-directory@2.1.1 checking installable status
28 silly pacote range manifest for set-blocking@^2.0.0 fetched in 346ms
29 silly resolveWithNewModule set-blocking@2.0.0 checking installable status
30 silly fetchPackageMetaData error for require-main-filename@^2.0.0 EACCES: permission denied, mkdir '/home/tanmay/.npm/_cacache/index-v5/00/78'
31 http fetch GET 304 https://registry.npmjs.org/cliui 358ms (from cache)
32 silly pacote range manifest for cliui@^5.0.0 fetched in 359ms
33 silly resolveWithNewModule cliui@5.0.0 checking installable status
34 http fetch GET 304 https://registry.npmjs.org/string-width 369ms (from cache)
35 silly pacote range manifest for string-width@^3.0.0 fetched in 370ms
36 silly resolveWithNewModule string-width@3.1.0 checking installable status
37 http fetch GET 304 https://registry.npmjs.org/yargs-parser 155ms (from cache)
38 silly pacote range manifest for yargs-parser@^13.1.0 fetched in 160ms
39 silly resolveWithNewModule yargs-parser@13.1.1 checking installable status
40 http fetch GET 304 https://registry.npmjs.org/get-caller-file 499ms (from cache)
41 silly pacote range manifest for get-caller-file@^2.0.1 fetched in 501ms
42 silly resolveWithNewModule get-caller-file@2.0.5 checking installable status
43 timing npm Completed in 1621ms
44 error cb() never called!
45 error This is an error with npm itself. Please report this error at:
46 error <https://npm.community>

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.