I cannot install angular. NPM error

Hi to all. I have a problem trying to install angular on my machine. I have angular before but due a some problems I decide to do a reinstall. The steps i took:

> npm uninstall -g @angular/cli
> npm cache verify
> npm install -g @angular/cli

But i cannot install Angular. The error i got:

Unhandled rejection Error: EISDIR: illegal operation on a directory, open '/Users/username/.npm/_cacache/content-v2/sha512/49/81'

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-08-03T21_24_42_806Z-debug.log

The log file:

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   'install',
1 verbose cli   '-g',
1 verbose cli   '@angular/cli' ]
2 info using npm@6.9.0
3 info using node@v8.11.3
4 verbose npm-session 54efa0a70d9a110e
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 304 https://registry.npmjs.org/@angular%2fcli 269ms (from cache)
8 silly pacote tag manifest for @angular/cli@latest fetched in 348ms
9 timing stage:loadCurrentTree Completed in 471ms
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 2ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule @angular/cli@8.2.0 checking installable status
17 http fetch GET 200 https://registry.npmjs.org/inquirer 278ms
18 http fetch GET 304 https://registry.npmjs.org/debug 333ms (from cache)
19 http fetch GET 304 https://registry.npmjs.org/ansi-colors 461ms (from cache)
20 http fetch GET 304 https://registry.npmjs.org/ini 470ms (from cache)
21 silly pacote range manifest for debug@^4.1.1 fetched in 536ms
22 silly resolveWithNewModule debug@4.1.1 checking installable status
23 silly pacote version manifest for ansi-colors@4.1.1 fetched in 539ms
24 silly resolveWithNewModule ansi-colors@4.1.1 checking installable status
25 silly pacote version manifest for inquirer@6.5.0 fetched in 552ms
26 silly resolveWithNewModule inquirer@6.5.0 checking installable status
27 silly pacote version manifest for ini@1.3.5 fetched in 588ms
28 silly resolveWithNewModule ini@1.3.5 checking installable status
29 http fetch GET 304 https://registry.npmjs.org/@angular-devkit%2fschematics 603ms (from cache)
30 http fetch GET 304 https://registry.npmjs.org/@schematics%2fupdate 623ms (from cache)
31 http fetch GET 304 https://registry.npmjs.org/@yarnpkg%2flockfile 626ms (from cache)
32 silly pacote version manifest for @angular-devkit/schematics@8.2.0 fetched in 682ms
33 silly resolveWithNewModule @angular-devkit/schematics@8.2.0 checking installable status
34 silly pacote version manifest for @yarnpkg/lockfile@1.1.0 fetched in 690ms
35 silly resolveWithNewModule @yarnpkg/lockfile@1.1.0 checking installable status
36 silly pacote version manifest for @schematics/update@0.802.0 fetched in 713ms
37 silly resolveWithNewModule @schematics/update@0.802.0 checking installable status
38 http fetch GET 304 https://registry.npmjs.org/@angular-devkit%2farchitect 723ms (from cache)
39 http fetch GET 304 https://registry.npmjs.org/@schematics%2fangular 724ms (from cache)
40 http fetch GET 304 https://registry.npmjs.org/@angular-devkit%2fcore 734ms (from cache)
41 silly pacote version manifest for @angular-devkit/architect@0.802.0 fetched in 763ms
42 silly resolveWithNewModule @angular-devkit/architect@0.802.0 checking installable status
43 silly pacote version manifest for @schematics/angular@8.2.0 fetched in 762ms
44 silly resolveWithNewModule @schematics/angular@8.2.0 checking installable status
45 silly pacote version manifest for @angular-devkit/core@8.2.0 fetched in 796ms
46 silly resolveWithNewModule @angular-devkit/core@8.2.0 checking installable status
47 http fetch GET 304 https://registry.npmjs.org/npm-package-arg 259ms (from cache)
48 http fetch GET 304 https://registry.npmjs.org/pacote 242ms (from cache)
49 silly pacote version manifest for npm-package-arg@6.1.0 fetched in 288ms
50 silly resolveWithNewModule npm-package-arg@6.1.0 checking installable status
51 http fetch GET 200 https://registry.npmjs.org/read-package-tree 241ms
52 silly pacote version manifest for pacote@9.5.4 fetched in 309ms
53 silly resolveWithNewModule pacote@9.5.4 checking installable status
54 http fetch GET 304 https://registry.npmjs.org/semver 260ms (from cache)
55 http fetch GET 304 https://registry.npmjs.org/symbol-observable 247ms (from cache)
56 silly pacote version manifest for semver@6.3.0 fetched in 265ms
57 silly resolveWithNewModule semver@6.3.0 checking installable status
58 silly pacote version manifest for symbol-observable@1.2.0 fetched in 251ms
59 silly resolveWithNewModule symbol-observable@1.2.0 checking installable status
60 silly pacote version manifest for read-package-tree@5.3.1 fetched in 415ms
61 silly resolveWithNewModule read-package-tree@5.3.1 checking installable status
62 http fetch GET 304 https://registry.npmjs.org/universal-analytics 280ms (from cache)
63 silly pacote range manifest for universal-analytics@^0.4.20 fetched in 306ms
64 silly resolveWithNewModule universal-analytics@0.4.20 checking installable status
65 http fetch GET 304 https://registry.npmjs.org/uuid 306ms (from cache)
66 silly pacote range manifest for uuid@^3.3.2 fetched in 366ms
67 silly resolveWithNewModule uuid@3.3.2 checking installable status
68 http fetch GET 304 https://registry.npmjs.org/open 853ms (from cache)
69 silly pacote version manifest for open@6.4.0 fetched in 855ms
70 silly resolveWithNewModule open@6.4.0 checking installable status
71 http fetch GET 304 https://registry.npmjs.org/rxjs 55ms (from cache)
72 silly pacote version manifest for rxjs@6.4.0 fetched in 73ms
73 silly resolveWithNewModule rxjs@6.4.0 checking installable status
74 http fetch GET 304 https://registry.npmjs.org/ajv 149ms (from cache)
75 http fetch GET 304 https://registry.npmjs.org/fast-json-stable-stringify 210ms (from cache)
76 http fetch GET 304 https://registry.npmjs.org/source-map 214ms (from cache)
77 silly pacote version manifest for ajv@6.10.2 fetched in 229ms
78 silly resolveWithNewModule ajv@6.10.2 checking installable status
79 silly pacote version manifest for source-map@0.7.3 fetched in 246ms
80 silly resolveWithNewModule source-map@0.7.3 checking installable status
81 silly pacote version manifest for fast-json-stable-stringify@2.0.0 fetched in 275ms
82 silly resolveWithNewModule fast-json-stable-stringify@2.0.0 checking installable status
83 http fetch GET 304 https://registry.npmjs.org/magic-string 310ms (from cache)
84 silly pacote version manifest for magic-string@0.25.3 fetched in 393ms
85 silly resolveWithNewModule magic-string@0.25.3 checking installable status
86 http fetch GET 304 https://registry.npmjs.org/json-schema-traverse 106ms (from cache)
87 silly pacote range manifest for json-schema-traverse@^0.4.1 fetched in 133ms
88 silly resolveWithNewModule json-schema-traverse@0.4.1 checking installable status
89 http fetch GET 304 https://registry.npmjs.org/fast-deep-equal 173ms (from cache)
90 silly pacote range manifest for fast-deep-equal@^2.0.1 fetched in 192ms
91 silly resolveWithNewModule fast-deep-equal@2.0.1 checking installable status
92 http fetch GET 304 https://registry.npmjs.org/uri-js 245ms (from cache)
93 silly pacote range manifest for uri-js@^4.2.2 fetched in 270ms
94 silly resolveWithNewModule uri-js@4.2.2 checking installable status
95 http fetch GET 304 https://registry.npmjs.org/punycode 103ms (from cache)
96 silly pacote range manifest for punycode@^2.1.0 fetched in 135ms
97 silly resolveWithNewModule punycode@2.1.1 checking installable status
98 http fetch GET 304 https://registry.npmjs.org/sourcemap-codec 106ms (from cache)
99 silly pacote range manifest for sourcemap-codec@^1.4.4 fetched in 137ms
100 silly resolveWithNewModule sourcemap-codec@1.4.6 checking installable status
101 http fetch GET 304 https://registry.npmjs.org/tslib 128ms (from cache)
102 silly pacote range manifest for tslib@^1.9.0 fetched in 155ms
103 silly resolveWithNewModule tslib@1.10.0 checking installable status
104 http fetch GET 304 https://registry.npmjs.org/semver-intersect 54ms (from cache)
105 silly pacote version manifest for semver-intersect@1.4.0 fetched in 56ms
106 silly resolveWithNewModule semver-intersect@1.4.0 checking installable status
107 http fetch GET 304 https://registry.npmjs.org/glob 111ms (from cache)
108 http fetch GET 304 https://registry.npmjs.org/get-stream 116ms (from cache)
109 silly pacote range manifest for glob@^7.1.3 fetched in 119ms
110 silly resolveWithNewModule glob@7.1.4 checking installable status
111 silly pacote range manifest for get-stream@^4.1.0 fetched in 156ms
112 silly resolveWithNewModule get-stream@4.1.0 checking installable status
113 http fetch GET 304 https://registry.npmjs.org/minipass 154ms (from cache)
114 http fetch GET 304 https://registry.npmjs.org/mississippi 155ms (from cache)
115 http fetch GET 304 https://registry.npmjs.org/figgy-pudding 162ms (from cache)
116 http fetch GET 304 https://registry.npmjs.org/cacache 162ms (from cache)
117 http fetch GET 304 https://registry.npmjs.org/lru-cache 177ms (from cache)
118 http fetch GET 304 https://registry.npmjs.org/make-fetch-happen 176ms (from cache)
119 silly pacote range manifest for minipass@^2.3.5 fetched in 239ms
120 silly resolveWithNewModule minipass@2.3.5 checking installable status
121 silly pacote range manifest for mississippi@^3.0.0 fetched in 242ms
122 silly resolveWithNewModule mississippi@3.0.0 checking installable status
123 silly pacote range manifest for figgy-pudding@^3.5.1 fetched in 249ms
124 silly resolveWithNewModule figgy-pudding@3.5.1 checking installable status
125 silly pacote range manifest for lru-cache@^5.1.1 fetched in 252ms
126 silly resolveWithNewModule lru-cache@5.1.1 checking installable status
127 http fetch GET 304 https://registry.npmjs.org/minimatch 298ms (from cache)
128 silly pacote range manifest for minimatch@^3.0.4 fetched in 364ms
129 silly resolveWithNewModule minimatch@3.0.4 checking installable status
130 silly pacote range manifest for make-fetch-happen@^5.0.0 fetched in 469ms
131 silly resolveWithNewModule make-fetch-happen@5.0.0 checking installable status
132 silly pacote range manifest for cacache@^12.0.0 fetched in 478ms
133 silly resolveWithNewModule cacache@12.0.2 checking installable status
134 http fetch GET 304 https://registry.npmjs.org/bluebird 608ms (from cache)
135 http fetch GET 304 https://registry.npmjs.org/mkdirp 502ms (from cache)
136 http fetch GET 304 https://registry.npmjs.org/npm-pick-manifest 398ms (from cache)
137 silly pacote range manifest for bluebird@^3.5.3 fetched in 650ms
138 silly resolveWithNewModule bluebird@3.5.5 checking installable status
139 http fetch GET 304 https://registry.npmjs.org/npm-registry-fetch 419ms (from cache)
140 silly pacote range manifest for npm-pick-manifest@^2.2.3 fetched in 436ms
141 silly resolveWithNewModule npm-pick-manifest@2.2.3 checking installable status
142 http fetch GET 304 https://registry.npmjs.org/npm-packlist 445ms (from cache)
143 silly pacote range manifest for mkdirp@^0.5.1 fetched in 589ms
144 silly resolveWithNewModule mkdirp@0.5.1 checking installable status
145 silly pacote range manifest for npm-packlist@^1.1.12 fetched in 469ms
146 silly resolveWithNewModule npm-packlist@1.4.4 checking installable status
147 http fetch GET 304 https://registry.npmjs.org/normalize-package-data 604ms (from cache)
148 silly pacote range manifest for semver@^5.6.0 fetched in 54ms
149 silly resolveWithNewModule semver@5.7.0 checking installable status
150 http fetch GET 304 https://registry.npmjs.org/promise-retry 435ms (from cache)
151 silly pacote range manifest for npm-registry-fetch@^4.0.0 fetched in 663ms
152 silly resolveWithNewModule npm-registry-fetch@4.0.0 checking installable status
153 silly pacote range manifest for promise-retry@^1.1.1 fetched in 455ms
154 silly resolveWithNewModule promise-retry@1.1.1 checking installable status
155 http fetch GET 304 https://registry.npmjs.org/protoduck 453ms (from cache)
156 silly pacote range manifest for normalize-package-data@^2.4.0 fetched in 775ms
157 silly resolveWithNewModule normalize-package-data@2.5.0 checking installable status
158 http fetch GET 304 https://registry.npmjs.org/osenv 741ms (from cache)
159 silly pacote range manifest for protoduck@^5.0.1 fetched in 587ms
160 silly resolveWithNewModule protoduck@5.0.1 checking installable status
161 http fetch GET 304 https://registry.npmjs.org/promise-inflight 701ms (from cache)
162 silly pacote range manifest for osenv@^0.1.5 fetched in 834ms
163 silly resolveWithNewModule osenv@0.1.5 checking installable status
164 silly pacote range manifest for promise-inflight@^1.0.1 fetched in 758ms
165 silly resolveWithNewModule promise-inflight@1.0.1 checking installable status
166 http fetch GET 304 https://registry.npmjs.org/tar 386ms (from cache)
167 silly pacote range manifest for tar@^4.4.8 fetched in 419ms
168 silly resolveWithNewModule tar@4.4.10 checking installable status
169 http fetch GET 304 https://registry.npmjs.org/rimraf 546ms (from cache)
170 http fetch GET 304 https://registry.npmjs.org/safe-buffer 513ms (from cache)
171 http fetch GET 304 https://registry.npmjs.org/ssri 486ms (from cache)
172 silly pacote range manifest for ssri@^6.0.1 fetched in 491ms
173 silly resolveWithNewModule ssri@6.0.1 checking installable status
174 http fetch GET 304 https://registry.npmjs.org/unique-filename 294ms (from cache)
175 silly pacote range manifest for rimraf@^2.6.2 fetched in 561ms
176 silly resolveWithNewModule rimraf@2.6.3 checking installable status
177 silly pacote range manifest for safe-buffer@^5.1.2 fetched in 540ms
178 silly resolveWithNewModule safe-buffer@5.2.0 checking installable status
179 silly pacote range manifest for unique-filename@^1.1.1 fetched in 322ms
180 silly resolveWithNewModule unique-filename@1.1.1 checking installable status
181 http fetch GET 304 https://registry.npmjs.org/which 312ms (from cache)
182 silly pacote range manifest for which@^1.3.1 fetched in 368ms
183 silly resolveWithNewModule which@1.3.1 checking installable status
184 http fetch GET 304 https://registry.npmjs.org/chownr 281ms (from cache)
185 silly pacote range manifest for chownr@^1.1.1 fetched in 303ms
186 silly resolveWithNewModule chownr@1.1.2 checking installable status
187 http fetch GET 304 https://registry.npmjs.org/graceful-fs 400ms (from cache)
188 http fetch GET 304 https://registry.npmjs.org/move-concurrently 401ms (from cache)
189 http fetch GET 304 https://registry.npmjs.org/y18n 409ms (from cache)
190 silly pacote range manifest for move-concurrently@^1.0.1 fetched in 419ms
191 silly resolveWithNewModule move-concurrently@1.0.1 checking installable status
192 silly pacote range manifest for y18n@^4.0.0 fetched in 427ms
193 silly resolveWithNewModule y18n@4.0.0 checking installable status
194 silly pacote range manifest for graceful-fs@^4.1.15 fetched in 441ms
195 silly resolveWithNewModule graceful-fs@4.2.0 checking installable status
196 timing npm Completed in 5750ms
197 error cb() never called!
198 error This is an error with npm itself. Please report this error at:
199 error <https://npm.community>

I dont know what else i could do. Thanks in advance.

PD: I’m new, maybe I don’t do the right thing posting this here, or maybe this is not the way it should be posted. Let me know if I do it wrong.

Hi @Assavar! This should be fixed by updating npm to 6.10.1: Release: npm@6.10.1

1 Like

Hi @shadowspawn first thing first. Thanks for replying so quickly. I can’t update npm either. I’ve the same error. I’ve forgot to mention i’m running on macOS 10.11.6

Unhandled rejection Error: EISDIR: illegal operation on a directory, open '/Users/username/.npm/_cacache/content-v2/sha512/cb/19'

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-08-05T18_57_27_919Z-debug.log

The log file:

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 ‘npm@latest’ ]
2 info using npm@6.9.0
3 info using node@v8.11.3
4 verbose npm-session 21973ad080d50c74
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 timing npm Completed in 10533ms
8 error cb() never called!
9 error This is an error with npm itself. Please report this error at:
10 error https://npm.community

PD: I’ve done the npm i -g npm@latest command

@shadowspawn I think this post has the same problems. Should I delete mine?

1 Like

Well found. There are lots of duplicates, but closing as solved or deleting would be good. Thanks for offering!

Well,I made it.

As simple as delete all the files stored in .npm folder.

sudo rm -rf ~/.npm

Download again nodeJS (12.7.0 has the one with npm 6.10) and done.

Node asks you if you have the usr/local/bin in the $PATH variable. As simple as:

echo $PATH

and search the string

Maybe its not a solution for everybody, but in my case works!

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