search

zkat / make-fetch-happen

Get in loser, we're making requests!
Other
384 stars 27 forks source link

Deploy on Azure failed #52

Closed ranouf closed 6 years ago

ranouf commented 6 years ago

Hi,

I have a problem when I deploy my angular app with your package: npm install npm ERR! path D:\home\site\repository\src\client\node_modules.staging\npm-d4c06741\node_modules\libnpmhook\node_modules\npm-registry-fetch\node_modules\make-fetch-happen\node_modules\http-proxy-agent\node_modules\agent-base\node_modules\es6-promisify\node_modules\es6-promise npm ERR! code EINVAL npm ERR! errno -4071 npm ERR! syscall rename npm ERR! EINVAL: invalid argument, rename 'D:\home\site\repository\src\client\node_modules.staging\npm-d4c06741\node_modules\libnpmhook\node_modules\npm-registry-fetch\node_modules\make-fetch-happen\node_modules\http-proxy-agent\node_modules\agent-base\node_modules\es6-promisify\node_modules\es6-promise' -> 'D:\home\site\repository\src\client\node_modules.staging\es6-promise-3ac93eae'

The problem is due to Azure who have issue to rename long path, Is there a way on your side to help me to fix this issue?

Probably not, but I tried so many different solutions which didnt work that now, I try other possibilities.

Thanks

zkat commented 6 years ago

This seems like a weird Windows/npm bug, not a bug with m-f-h itself.