At the end, I would suggest anyone who is facing the same problem to use codespace for temporary development solution.Red giant magic bullet serial key OctoRed giant magic bullet serial key I can't come to a conclusion, as the same repo was having problems in local machine but then on codespaces it worked like a charm. But this time I waited for a while, and ultimately it did finish installing the libraries. When I went back to my initial project, it still had problems with npm i. In my case, I thought I may have broken something in powershell, however when I created a new project, npm i is running fine. Try to create a new project and then run npm i again. It is quite possible that the project is using some library and that library has problems. Go for the soft reset first where you would not loose your data. However, not everyone can afford to reset pc so, temporarily use yarn and then prepare for a reset. I observed this issue in another pc and after resetting the pc, npm i was working fine. if yarn works then my conclusion is something must be broken in windows powershell.Please, if anyone knows, I would greatly appreciate it the explanation. So I just ran the npm install in git bash and solved inmediately without any issue. I am also ran into this problem that the npm get stuck forever while running on the Windows 10 powershell. Thanks a lot to mention the git bash terminal solution this save me. My git version installed on windows was 2.17.1.windows.2. I then switched to a git bash terminal and was able to run npm install 3 times with version 16.13.1/8.1.2 and no hangs. I was also running Fiddler4 and haven't seen any HTTP errors related. I do have AV Defender installed, which I can't disable due to it being a company installed anti-virus software. I've tried the following combinations and was able to reproduce the stuckness each time (I was using nvm for windows to switch versions): I am getting this error as well on a windows PC using the command prompt (cmd.exe). If it succeeds, repeat the above steps until the freeze is observed.Clear down the node_modules folder (ie with something like rmdir /q /s).If it gets stuck it should either time-out or be closable by the user. Npm install should either succeed or show an error. Does anyone have any advice on how to investigate this, or at the very least a way to kill the process when it hangs like this without having to reboot the machine? Being forced to reboot when this issue occurs is perhaps the most frustrating thing in all of this. I've seen this issue occur on different projects, on different network and internet connections, and on different machines. The only thing that I can think of right now is that Bit Defender (the only other application running) is interfering somehow, however it's the one application I can't turn off. Npm timing reifyNode:node_modules/ajv-formats/node_modules/ajv Completed in 56497ms Npm timing reifyNode:node_modules/regenerate-unicode-properties Completed in 55637ms Npm timing reifyNode:node_modules/selenium-webdriver Completed in 54728ms Npm timing reify:audit Completed in 55729ms Npm timing auditReport:init Completed in 49242ms This is some log output from one of the times when it got stuck (I should again emphasise that the point where it gets stuck seems to be random, so the last line shown here isn't always the one it freezes on): When it freezes there are no warnings or errors, it just sits on the line it was on. There are handles held by the Node process npm is using, and one for the CMD window hosting it, but that's it.Įven running with log-level silly yields no useful information. I've tried using Process Explorer to check for handles to files in the project directory from other processes but there are none. My suspicion is it's some sort of deadlock, but this is a guess and I have no idea how to further investigate this. The only way I have found to close it is to reboot the machine. The process cannot be killed by Task Manager either (Access Denied, although I'm an Administrator user so I'd assume the real reason is something non-permissions related). The CMD (or Powershell) window cannot be closed regardless. No further responses to that key combination are observed. Pressing that key combination the second time will make the current line (the one showing the little progress bar) disappear but that's it. CTRL+C will do nothing the first time that combination is pressed when this has occurred. When running npm install it will sometimes hang at a random point. This issue exists in the latest npm version
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |