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 |