Error while installing iconify/icons-mdi version "1.0.149",

[iconify]

Error while installing iconify/icons-mdi version "1.0.149",

[cyberalien]

That's NPM installation process error, not a problem with package. Package cannot affect any of it.

[cyberalien]

Another thing to try: run npm ci instead of npm install. It will do a clean install

[Carniatto]

when running npm ci the error is not there. However, it always happens with npm install I don't understand why that

[cyberalien]

Both install and ci install dependencies, the only difference is ci does clean install. That is it ignores previously installed files.

So if you are getting error when using install, but not ci, there is something fishy going on with your file system or NPM cache. I'm not familiar enough with inner workings of NPM to debug its errors. One thing I know that might help is npm cache clean --force that will clear cache.

[Carniatto]

The difference between npm install and npm ci is that the first uses package.json and the second uses package-lock.json. Link

These are the steps I performed:
1 - created a new folder
2 - cleaned the cache with npm cache clean --force
3 - tried npm i @iconify/icons-mdi

However, I still got the error.

My specs are:

MacOs: 10.15.5
node: v12.9.1
npm: 6.14.8

See below the npm log:

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/Users/matt/.nvm/versions/node/v12.9.1/bin/node',
1 verbose cli   '/Users/matt/.nvm/versions/node/v12.9.1/bin/npm',
1 verbose cli   'i',
1 verbose cli   '@iconify/icons-mdi@latest'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose npm-session 32af07ad5b82af9c
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 http fetch GET 200 https://registry.npmjs.org/@iconify%2ficons-mdi 328ms
8 http fetch GET 200 https://registry.npmjs.org/@iconify/icons-mdi/-/icons-mdi-1.0.150.tgz 698ms
9 silly pacote tag manifest for @iconify/icons-mdi@latest fetched in 1044ms
10 timing stage:loadCurrentTree Completed in 1067ms
11 silly install loadIdealTree
12 silly install cloneCurrentTreeToIdealTree
13 timing stage:loadIdealTree:cloneCurrentTree Completed in 1ms
14 silly install loadShrinkwrap
15 timing stage:loadIdealTree:loadShrinkwrap Completed in 0ms
16 silly install loadAllDepsIntoIdealTree
17 silly resolveWithNewModule @iconify/[email protected] checking installable status
18 timing stage:loadIdealTree:loadAllDepsIntoIdealTree Completed in 4ms
19 timing stage:loadIdealTree Completed in 6ms
20 silly currentTree [email protected]
21 silly idealTree [email protected]
21 silly idealTree └── @iconify/[email protected]
22 silly install generateActionsToTake
23 timing stage:generateActionsToTake Completed in 3ms
24 silly diffTrees action count 1
25 silly diffTrees add @iconify/[email protected]
26 silly decomposeActions action count 8
27 silly decomposeActions fetch @iconify/[email protected]
28 silly decomposeActions extract @iconify/[email protected]
29 silly decomposeActions preinstall @iconify/[email protected]
30 silly decomposeActions build @iconify/[email protected]
31 silly decomposeActions install @iconify/[email protected]
32 silly decomposeActions postinstall @iconify/[email protected]
33 silly decomposeActions finalize @iconify/[email protected]
34 silly decomposeActions refresh-package-json @iconify/[email protected]
35 silly install executeActions
36 silly doSerial global-install 8
37 verbose correctMkdir /Users/matt/.npm/_locks correctMkdir not in flight; initializing
38 verbose lock using /Users/matt/.npm/_locks/staging-83b5ef8f1d41518b.lock for /Users/matt/dev/Riaktr/test2/node_modules/.staging
39 silly doParallel extract 1
40 silly extract @iconify/[email protected]
41 silly tarball trying @iconify/icons-mdi@latest by hash: sha512-/4ZAjYiMuv50F9oz4rkiwyuuEDGlAj/m3MBEM9NCPjs2+2WmOvO3pdENCNeFyWYISeIF4vP1wYPzFsn65uDGcQ==
42 timing audit submit Completed in 252ms
43 http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/audits/quick 251ms
44 timing audit body Completed in 1ms
45 silly extract @iconify/icons-mdi@latest extracted to /Users/matt/dev/Riaktr/test2/node_modules/.staging/@iconify/icons-mdi-bdf166d4 (5281ms)
46 timing action:extract Completed in 5284ms
47 silly doReverseSerial unbuild 8
48 silly doSerial remove 8
49 silly doSerial move 8
50 silly doSerial finalize 8
51 silly finalize /Users/matt/dev/Riaktr/test2/node_modules/@iconify/icons-mdi
52 timing action:finalize Completed in 100037ms
53 verbose unlock done using /Users/matt/.npm/_locks/staging-83b5ef8f1d41518b.lock for /Users/matt/dev/Riaktr/test2/node_modules/.staging
54 timing stage:rollbackFailedOptional Completed in 1ms
55 timing stage:runTopLevelLifecycles Completed in 110035ms
56 silly saveTree [email protected]
56 silly saveTree └── @iconify/[email protected]
57 warn [email protected] No description
58 warn [email protected] No repository field.
59 verbose stack Error: ENOENT: no such file or directory, rename '/Users/matt/dev/Riaktr/test2/node_modules/@iconify/icons-mdi' -> '/Users/matt/dev/Riaktr/test2/node_modules/@iconify/.icons-mdi.DELETE'
60 verbose cwd /Users/matt/dev/Riaktr/test2
61 verbose Darwin 19.5.0
62 verbose argv "/Users/matt/.nvm/versions/node/v12.9.1/bin/node" "/Users/matt/.nvm/versions/node/v12.9.1/bin/npm" "i" "@iconify/icons-mdi@latest"
63 verbose node v12.9.1
64 verbose npm  v6.14.8
65 error code ENOENT
66 error syscall rename
67 error path /Users/matt/dev/Riaktr/test2/node_modules/@iconify/icons-mdi
68 error dest /Users/matt/dev/Riaktr/test2/node_modules/@iconify/.icons-mdi.DELETE
69 error errno -2
70 error enoent ENOENT: no such file or directory, rename '/Users/matt/dev/Riaktr/test2/node_modules/@iconify/icons-mdi' -> '/Users/matt/dev/Riaktr/test2/node_modules/@iconify/.icons-mdi.DELETE'
71 error enoent This is related to npm not being able to find a file.
72 verbose exit [ -2, true ]

[cyberalien]

Try updating to Node to version 15 and NPM to version 7. It uses completely different installation process, maybe that issue will go away.

[Carniatto]

Already tried that. It is indeed something in my filesystem cuz it works inside a docker container. However is always this library in any folder.

[cyberalien]

If your code can work with ES modules, you can try switching to @iconify-icons/mdi. It is identical, except that it uses ES exports instead of CommonJS.

[Carniatto]

Thanks for the suggestion but now I get the same problem with this library. The funny thing is that the only npm package causing me the issue and I have dozens of projects in my machine with hundreds of npm packages

[cyberalien]

The only thing they have in common is high number of files. There is a separate file for each icon and for each alias. Then number of files is doubled because of TypeScript definition files. So that is over 10k files for material design set in one directory.

[cyberalien]

Closing this. Unfortunately there is no solution to having so many files in one package.

However, now there is a different icon component that generates icon data during bundling, which uses full icon set files to generate data, so this issue does not apply to it: http://github.com/antfu/unplugin-icons