[Angular] npm ERR! cb() never called!

What I Wanted to Do

make Angular PJ

What Happened Instead

ng new my-first-app

Reproduction Steps

ng new my-first-app
? Would you like to add Angular routing? No
? Which stylesheet format would you like to use? SCSS   [ http://sass-lang.com/documentation/file.SASS_REFERENCE.html#syntax ]
CREATE my-first-app/README.md (1027 bytes)
CREATE my-first-app/.editorconfig (246 bytes)
CREATE my-first-app/.gitignore (629 bytes)
CREATE my-first-app/angular.json (3561 bytes)
CREATE my-first-app/package.json (1285 bytes)
CREATE my-first-app/tsconfig.json (543 bytes)
CREATE my-first-app/tslint.json (1988 bytes)
CREATE my-first-app/browserslist (429 bytes)
CREATE my-first-app/karma.conf.js (1024 bytes)
CREATE my-first-app/tsconfig.app.json (210 bytes)
CREATE my-first-app/tsconfig.spec.json (270 bytes)
CREATE my-first-app/src/favicon.ico (5430 bytes)
CREATE my-first-app/src/index.html (297 bytes)
CREATE my-first-app/src/main.ts (372 bytes)
CREATE my-first-app/src/polyfills.ts (2838 bytes)
CREATE my-first-app/src/styles.scss (80 bytes)
CREATE my-first-app/src/test.ts (642 bytes)
CREATE my-first-app/src/assets/.gitkeep (0 bytes)
CREATE my-first-app/src/environments/environment.prod.ts (51 bytes)
CREATE my-first-app/src/environments/environment.ts (662 bytes)
CREATE my-first-app/src/app/app.module.ts (314 bytes)
CREATE my-first-app/src/app/app.component.scss (0 bytes)
CREATE my-first-app/src/app/app.component.html (1120 bytes)
CREATE my-first-app/src/app/app.component.spec.ts (996 bytes)
CREATE my-first-app/src/app/app.component.ts (217 bytes)
CREATE my-first-app/e2e/protractor.conf.js (810 bytes)
CREATE my-first-app/e2e/tsconfig.json (214 bytes)
CREATE my-first-app/e2e/src/app.e2e-spec.ts (641 bytes)
CREATE my-first-app/e2e/src/app.po.ts (251 bytes)
Unhandled rejection Error: EACCES: permission denied, open '/Users/username/.npm/_cacache/XXXXXXXX'

npm ERR! cb() never called!

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

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/username/.npm/_logs/2019-07-09T22_21_48_614Z-debug.log
Package install failed, see above.


0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/Users/username/.nodebrew/node/v12.6.0/bin/node',
1 verbose cli   '/Users/username/.nodebrew/current/bin/npm',
1 verbose cli   'install',
1 verbose cli   '--quiet'
1 verbose cli ]
2 info using npm@6.10.0
3 info using node@v12.6.0
4 verbose npm-session 1fbc5d38dc42b70f
5 silly install runPreinstallTopLevelLifecycles
6 silly preinstall my-first-app@0.0.0
7 info lifecycle my-first-app@0.0.0~preinstall: my-first-app@0.0.0
8 silly install loadCurrentTree
9 silly install readLocalPackageData
10 timing stage:loadCurrentTree Completed in 10ms
11 silly install loadIdealTree
12 silly install cloneCurrentTreeToIdealTree
13 timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms
14 silly install loadShrinkwrap
15 timing stage:loadIdealTree:loadShrinkwrap Completed in 3ms
16 silly install loadAllDepsIntoIdealTree
17 http fetch GET 200 https://registry.npmjs.org/codelyzer 175ms
18 http fetch GET 200 https://registry.npmjs.org/@types%2fjasminewd2 179ms
19 http fetch GET 200 https://registry.npmjs.org/@angular%2fcompiler-cli 183ms
20 http fetch GET 200 https://registry.npmjs.org/@angular%2flanguage-service 197ms
21 silly pacote range manifest for @angular/compiler-cli@~8.1.0 fetched in 204ms
22 silly pacote range manifest for codelyzer@^5.0.0 fetched in 199ms
23 silly pacote range manifest for @types/jasminewd2@~2.0.3 fetched in 200ms
24 http fetch GET 200 https://registry.npmjs.org/@types%2fnode 212ms
25 http fetch GET 304 https://registry.npmjs.org/@angular%2fcli 229ms (from cache)
26 silly pacote range manifest for @angular/language-service@~8.1.0 fetched in 252ms
27 silly pacote range manifest for @types/node@~8.9.4 fetched in 255ms
28 http fetch GET 200 https://registry.npmjs.org/karma-coverage-istanbul-reporter 48ms
29 http fetch GET 200 https://registry.npmjs.org/karma-chrome-launcher 52ms
30 silly pacote range manifest for @angular/cli@~8.1.0 fetched in 261ms
31 http fetch GET 200 https://registry.npmjs.org/karma 55ms
32 silly pacote range manifest for karma-coverage-istanbul-reporter@~2.0.1 fetched in 65ms
33 silly pacote range manifest for karma-chrome-launcher@~2.2.0 fetched in 68ms
34 silly pacote range manifest for karma@~4.1.0 fetched in 73ms
35 http fetch GET 200 https://registry.npmjs.org/karma-jasmine 30ms
36 silly pacote range manifest for karma-jasmine@~2.0.1 fetched in 43ms
37 http fetch GET 200 https://registry.npmjs.org/karma-jasmine-html-reporter 40ms
38 http fetch GET 200 https://registry.npmjs.org/protractor 33ms
39 http fetch GET 200 https://registry.npmjs.org/jasmine-core 295ms
40 silly pacote range manifest for karma-jasmine-html-reporter@^1.4.0 fetched in 60ms
41 silly pacote range manifest for protractor@~5.4.0 fetched in 54ms
42 silly pacote range manifest for jasmine-core@~3.4.0 fetched in 317ms
43 http fetch GET 200 https://registry.npmjs.org/@angular-devkit%2fbuild-angular 339ms
44 http fetch GET 200 https://registry.npmjs.org/ts-node 67ms
45 http fetch GET 200 https://registry.npmjs.org/@angular%2fanimations 46ms
46 http fetch GET 200 https://registry.npmjs.org/tslint 77ms
47 silly pacote range manifest for @angular-devkit/build-angular@~0.801.0 fetched in 382ms
48 silly pacote range manifest for ts-node@~7.0.0 fetched in 101ms
49 silly pacote range manifest for @angular/animations@~8.1.0 fetched in 84ms
50 http fetch GET 200 https://registry.npmjs.org/@angular%2fcore 61ms
51 silly pacote range manifest for tslint@~5.15.0 fetched in 118ms
"~/.npm/_logs/2019-07-09T22_21_48_614Z-debug.log" 2128L, 158654C

Platform Info

$ npm --versions
<!-- paste output here -->

$ node -p process.platform
<!-- paste output here -->

I can do it!!!

$ sudo npm cache clean --force
$ npm cache ls
$ rm -rf ~/.npm

This is a permissions issue, and the note from @D-Nancy should fix it. But, it would be helpful if you could share what the XXXXXX is in the error output. (The hex and base64 bits there are content hashes, not passwords.)

If I know what kind of thing it’s failing to load from cache, I could reproduce and at least get it to return a more helpful error message.