cli: Failed to install node version '12.18.0'
Describe the bug It was working fine few days ago, until today. I made some changes in the app (nothing related to npm) and it fail to deploy.
DEPLOY LOG:
1:57:42 PM: Build ready to start
1:57:44 PM: build-image version: b0258b965567defc4a2d7e2f2dec2e00c8f73ad6
1:57:44 PM: build-image tag: v3.4.1
1:57:44 PM: buildbot version: fcbc7a79f7372e5995cf02954ef19fc48d20c871
1:57:44 PM: Fetching cached dependencies
1:57:44 PM: Starting to download cache of 111.6MB
1:57:45 PM: Finished downloading cache in 931.829534ms
1:57:45 PM: Starting to extract cache
1:57:50 PM: Finished extracting cache in 5.155362108s
1:57:50 PM: Finished fetching cache in 6.12420572s
1:57:50 PM: Starting to prepare the repo for build
1:57:51 PM: Preparing Git Reference refs/heads/master
1:57:52 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: 'build' versus 'build/' in the Netlify UI
1:57:52 PM: Starting build script
1:57:52 PM: Installing dependencies
1:57:52 PM: Python version set to 2.7
1:57:53 PM: Started restoring cached node version
1:57:56 PM: Finished restoring cached node version
1:58:12 PM: Version '12.18.0' not found - try `nvm ls-remote` to browse available versions.
1:58:12 PM: Failed to install node version '12.18.0'
1:58:12 PM: Error running command: Build script returned non-zero exit code: 1
1:58:12 PM: Failing build: Failed to build site
1:58:12 PM: Failed during stage 'building site': Build script returned non-zero exit code: 1
1:58:12 PM: Finished processing build request in 28.285263389s
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 7
- Comments: 43 (4 by maintainers)
this is a bug… I have the same issue, they might fix it soon
Setting NODE_ENV to 14 worked for me
Ah! developers! 🤣
Or someone can fixes it and sends PR for them???
I’m surprised at how fast google indexed this as the first result.
Btw #metoo
I just made a build and their is no problems.
Hi @noerbot,
Thanks for reporting. This was due to a problem with npm itself, which has now been fixed.
They’re investigating - https://www.netlifystatus.com/incidents/sbl67cwypcf0
Same here !!! I hope they fix it soon