挂起/卡住 reify:prettier: 定时 reifyNode:node_modules/@nrwl/workspace 12729ms 完成

Question

细节：

? 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

工具版本

• npm 7.6.1

• 纱线 1.22.5

• 节点 v15.12.0

Answer 1

现在都2022年了，这个问题依然存在。我使用的是 Node.js 16.x/npm 8。为了解决这个问题，我简单地降级到 Node.js 14.x/npm 6。

Answer 2

现在安装软件包时使用 npm 8 仍然存在问题opencv-build，可以通过工程降级到 npm 6 npm install -g npm@6。

Answer 3

就我而言，按Ctrl+C显示它只是下载一些东西：

\n

...\n\nnpm ERR!      0K .......... ..........                                 100%  149K=0.1s\nnpm ERR!\nnpm ERR! 2021-12-24 16:11:52 (149 KB/s) - \xe2\x80\x98/tmp/install_wasmedge.sh\xe2\x80\x99 saved [21372/21372]\nnpm ERR!\nnpm ERR!\nnpm ERR!      0K .......... .......... .......... .......... ..........  0%  196K 3m23s\nnpm ERR!     50K .......... .......... .......... .......... ..........  0% 77.5K 5m58s\nnpm ERR!    100K .......... .......... .......... .......... ..........  0%  125M 3m58s\nnpm ERR!    150K .......... .......... .......... .......... ..........  0%  104K 4m34s\nnpm ERR!    200K .......... .......... .......... .......... ..........  0%  115K 4m48s\nnpm ERR!    250K .......... .......... .......... .......... ..........  0% 22.7K 8m50s\nnpm ERR!    300K .......... .......... .......... .......... ..........  0% 42.6K 9m46s\nnpm ERR!    350K .......... .......... .......... .......... ..........  1% 34.1K 10m57s\nnpm ERR!    400K .......... .......... .......... .......... ..........  1% 30.5K 12m7s\nnpm ERR!    450K .......... .......... .......... .......... ..........  1% 16.5K 14m52s\n\n...\n\nnpm ERR!  16950K .......... .......... .......... .......... .......... 42% 26.6K 21m45s\nnpm ERR!  17000K .......... .......... .......... .......... .......... 42% 20.5K 21m41s\nnpm ERR!  17050K .......... .......... .......... .......... .......... 42% 16.4K 21m39s\nnpm ERR!  17100K .......... .......... .......... .......... .......... 43% 14.2K 21m37s\nnpm ERR!  17150K .......... .......... .......... .......... .......... 43% 14.0K 21m35s\nnpm ERR!  17200K .......... .......... .......... .......... .......... 43% 31.7K 21m30s\nnpm ERR!  17250K .......... .......... .......... .......... .......... 43% 27.6K 21m26s\nnpm ERR!  17300K .......... .......... .......... .......... .......... 43% 25.6K 21m22s\nnpm ERR!  17350K .......... .......... .......... .......... .......... 43% 15.1K 21m20s\nnpm ERR!  17400K .......... .......... .......... .......... .......... 43% 18.9K 21m17s\nnpm ERR!  17450K .......... .......... .\n

\n

=> 查看您的网络流量日志。

\n

Answer 4

同样在这里。节点 18.12.1 npm 8.19.2

唯一的解决方案是降级到 npm v6npm install -g npm@6

Answer 5

我遇到了同样的错误，并通过使用使用 npm 6 的 node v12.0 修复了它，我很确定该错误与 npm 7 相关联。

Answer 6

就我而言：问题出在 npm 7 上，我已经更改了 npm 的版本

sudo npm install -g npm@6

并重新运行命令并繁荣......它起作用了。

Answer 7

不，现在已经 2024 年了，问题仍然存在。