'Hanging/stuck reify:prettier: timing reifyNode:node_modules/@nrwl/workspace Completed in 12729ms
Details:
? Workspace name (e.g., org name) swag
? What to create in the new workspace angular-nest [a workspace with a full stack application (Angular + Nest)]
? Application name swag
? Default stylesheet format SASS(.scss) [ http://sass-lang.com ]
? Default linter ESLint [ Modern linting tool ]
? Use Nx Cloud? (It's free and doesn't require registration.) No
> NX Nx is creating your workspace.
To make sure the command works reliably in all environments, and that the preset is applied correctly,
Nx will run "npm install" several times. Please wait.
[.....................] \ reify:prettier: timing reifyNode:node_modules/@nrwl/workspace Completed in 12729ms
Tools versions
npm 7.6.1
yarn 1.22.5
node v15.12.0
Solution 1:[1]
I got the same error and got it fixed by using node v12.0 which uses npm 6, I am pretty sure the error is linked to npm 7.
Solution 2:[2]
Still a problem when using npm 8 when installing opencv-build package now, downgrade to npm 6 by npm install -g npm@6 works.
Solution 3:[3]
In my case, pressing Ctrl + C showed it had only downloading something:
...
npm ERR! 0K .......... .......... 100% 149K=0.1s
npm ERR!
npm ERR! 2021-12-24 16:11:52 (149 KB/s) - ‘/tmp/install_wasmedge.sh’ saved [21372/21372]
npm ERR!
npm ERR!
npm ERR! 0K .......... .......... .......... .......... .......... 0% 196K 3m23s
npm ERR! 50K .......... .......... .......... .......... .......... 0% 77.5K 5m58s
npm ERR! 100K .......... .......... .......... .......... .......... 0% 125M 3m58s
npm ERR! 150K .......... .......... .......... .......... .......... 0% 104K 4m34s
npm ERR! 200K .......... .......... .......... .......... .......... 0% 115K 4m48s
npm ERR! 250K .......... .......... .......... .......... .......... 0% 22.7K 8m50s
npm ERR! 300K .......... .......... .......... .......... .......... 0% 42.6K 9m46s
npm ERR! 350K .......... .......... .......... .......... .......... 1% 34.1K 10m57s
npm ERR! 400K .......... .......... .......... .......... .......... 1% 30.5K 12m7s
npm ERR! 450K .......... .......... .......... .......... .......... 1% 16.5K 14m52s
...
npm ERR! 16950K .......... .......... .......... .......... .......... 42% 26.6K 21m45s
npm ERR! 17000K .......... .......... .......... .......... .......... 42% 20.5K 21m41s
npm ERR! 17050K .......... .......... .......... .......... .......... 42% 16.4K 21m39s
npm ERR! 17100K .......... .......... .......... .......... .......... 43% 14.2K 21m37s
npm ERR! 17150K .......... .......... .......... .......... .......... 43% 14.0K 21m35s
npm ERR! 17200K .......... .......... .......... .......... .......... 43% 31.7K 21m30s
npm ERR! 17250K .......... .......... .......... .......... .......... 43% 27.6K 21m26s
npm ERR! 17300K .......... .......... .......... .......... .......... 43% 25.6K 21m22s
npm ERR! 17350K .......... .......... .......... .......... .......... 43% 15.1K 21m20s
npm ERR! 17400K .......... .......... .......... .......... .......... 43% 18.9K 21m17s
npm ERR! 17450K .......... .......... .
=> See your network traffic log.
Solution 4:[4]
It's 2022, and this problem still exists. I was using Node.js 16.x/npm 8. To solve this problem, I simply downgraded to Node.js 14.x/npm 6.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | Ãlvaro |
| Solution 2 | moontai0724 |
| Solution 3 | Mir-Ismaili |
| Solution 4 | simoncpu |