Home
Support Forums

Unable to build successfully - possibly NPM node version incompatibility issue

Hi there!

I can’t seem to figure out what is causing the error I am getting from my current deploy. A little research on the web makes me think that perhaps my node version does not match what Netlify is currently compatible with but I’m not sure!

We’ve also tried uploading an nvmrc file which was in an online solution but I’m not sure if that is going down the right path. Here is the log:

6:17:18 PM: Build ready to start

6:17:20 PM: build-image version: 653805ca4a64301556e56dc4b321ef8fc20cbb7c

6:17:20 PM: build-image tag: v3.8.2

6:17:20 PM: buildbot version: 27121fae4d1b3a5c621e9bbd5ca8c7f99e19f330

6:17:20 PM: Fetching cached dependencies

6:17:20 PM: Failed to fetch cache, continuing with build

6:17:20 PM: Starting to prepare the repo for build

6:17:21 PM: No cached dependencies found. Cloning fresh repo

6:17:21 PM: git clone WEBSITE URL hidden for privacy

6:17:23 PM: Preparing Git Reference refs/heads/master

6:17:24 PM: Parsing package.json dependencies

6:17:24 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: ‘public’ versus ‘public/’ in the Netlify UI

6:17:24 PM: Starting build script

6:17:24 PM: Installing dependencies

6:17:24 PM: Python version set to 2.7

6:17:25 PM: Attempting node version '��v14.15.0 ’ from .nvmrc

6:17:26 PM: Version '��v14.15.0 ’ not found - try nvm ls-remote to browse available versions.

6:17:26 PM: Failed to install node version '��v14.15.0 ’

6:17:26 PM: Build was terminated: Build script returned non-zero exit code: 1

6:17:26 PM: Creating deploy upload records

6:17:26 PM: Failing build: Failed to build site

6:17:26 PM: Failed during stage ‘building site’: Build script returned non-zero exit code: 1

6:17:26 PM: Finished processing build request in 5.662315215s

Ultimately I’m stuck! Please help! :slight_smile:

Much appreciated, thanks!

Welcome to the forums @EMMA1

The �� before the node version string indicates there is a character (or two) before the version string which the version if not resolved. If you haven’t, try running node -v > .nvmrc to make the file to ensure it is correct.