Hi I'm having issue while installing react-dom module.
I'm able install other modules like react express modules, on windows 10. 64 bit machine
npm install react-dom
npm WARN package.json -panel-client@1.0.0 No description
npm WARN package.json -panel-client@1.0.0 No repository field.
npm WARN package.json -panel-client@1.0.0 No README data
npm WARN package.json -panel-client@1.0.0 No license field.
npm WARN retry will retry, error on last attempt: Error: EBUSY: resource busy or locked, rename 'C:\Users\NOI-DE~1\AppData\Local\Temp\npm-3064-f12f714d\registry.npmjs.org\react-dom\-\react-dom-0.14.8.tgz.2090210803' -> 'C:\Users\NOI-DE~1\AppData\Local\Temp\npm-3064-f12f714d\registry.npmjs.org\react-dom\-\react-dom-0.14.8.tgz'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "react-dom"
npm ERR! node v4.4.3
npm ERR! npm v2.15.1
npm ERR! tarball.destroy is not a function
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm WARN retry will retry, error on last attempt: Error: EBUSY: resource busy or locked, rename 'C:\Users\NOI-DE~1\AppData\Local\Temp\npm-3064-f12f714d\registry.npmjs.org\react-dom\-\react-dom-0.14.8.tgz.2000813013' -> 'C:\Users\NOI-DE~1\AppData\Local\Temp\npm-3064-f12f714d\registry.npmjs.org\react-dom\-\react-dom-0.14.8.tgz'
I was using npm in dell machine. I met the same issue (tarball.destroy is not a function). At the time I had installed anti-malware software. Then I had uninstalled it, then npm working fine. This is my suggestion.
I found mentioned folder (e.g 'npm-3064-f12f714d') unmarked as being readonly and I think that helped. The difference also was that I run command from cmd and earlier I did it from VS Code, but I think it doesn't matter.
Reason : anti-malware software
Try : uninstall "ByteFence" named application
I had the same issue before. On removing anti-malware(ByteFence) it worked like a charm.
Try disabling the antivirus and then run it. It worked for me.
I got this error when I was out of disk space.
Deleting my /root/dump files, and dropping a very large mongo db, then doing a server reboot fixed this issue for me.