# Same Source Code: Build failure on one site and not an another site

**URL:** <https://answers.netlify.com/t/same-source-code-build-failure-on-one-site-and-not-an-another-site/74129>\
**Category:** Support\
**Tags:** building\
**Created:** [August 24, 2022, 3:07am UTC](https://answers.netlify.com/t/same-source-code-build-failure-on-one-site-and-not-an-another-site/74129 "2022-08-24T03:07:21Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![haigopi](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/haigopi/32/40600_2.png) [@haigopi](https://answers.netlify.com/u/haigopi)\
**Post date:** [August 24, 2022, 3:07am UTC](https://answers.netlify.com/t/same-source-code-build-failure-on-one-site-and-not-an-another-site/74129/1 "2022-08-24T03:07:21Z")

</div>

PLEASE help us help you by writing a good post!

- we need to know your netlify site name. Example: `https://vantashala.netlify.app/`
- Build problems? Link or paste the FULL build log & build settings screenshot  
log: [Netlify App](https://app.netlify.com/sites/vantashala/deploys/630555cbb554c60008071e26)

My source code repository is the same and it is building and deploying good on one site and not on another site.  
Successful deployment: vsdevqa.netlify.app  
Failing to build on: vantashala.netlify.app

Error log:  
5:43:33 PM: 63 │ ‘sm’: $grid-gutter / 6npm ERR! code ELIFECYCLE  
5:43:33 PM: npm ERR! errno 1  
5:43:33 PM: npm ERR! vantashala@0.1.0 build: `vue-cli-service build`  
5:43:33 PM: npm ERR! Exit status 1  
5:43:33 PM: npm ERR!  
5:43:33 PM: npm ERR! Failed at the vantashala@0.1.0 build script.  
5:43:33 PM: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.  
5:43:34 PM: npm ERR! A complete log of this run can be found in:  
5:43:34 PM: npm ERR! /opt/buildhome/.npm/\_logs/2022-08-23T22\_42\_47\_547Z-debug.log  
5:43:34 PM: ​  
5:43:34 PM: ────────────────────────────────────────────────────────────────  
5:43:34 PM: “build.command” failed  
5:43:34 PM: ────────────────────────────────────────────────────────────────  
5:43:34 PM: ​  
5:43:34 PM: Error message  
5:43:34 PM: Command failed with exit code 1: npm run build ([Search results for '"non-zero exit code: 1"' - Netlify Support Forums](https://ntl.fyi/exit-code-1))  
5:43:34 PM: ​  
5:43:34 PM: Error location  
5:43:34 PM: In Build command from Netlify app:  
5:43:34 PM: npm run build

---

<div class="post-metadata">

**Author:** ![luke](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/luke/32/39_2.png) [@luke](https://answers.netlify.com/u/luke)\
**Post date:** [August 24, 2022, 7:28am UTC](https://answers.netlify.com/t/same-source-code-build-failure-on-one-site-and-not-an-another-site/74129/2 "2022-08-24T07:28:32Z")

</div>

Hi, @haigopi. The working build logs show this:

```plaintext
3:34:25 PM: Now using node v14.20.0 (npm v6.14.17)

```

The non-working build logs show this:

```plaintext
8:12:38 PM: Now using node v12.18.0 (npm v6.14.4)

```

So, the first thing I recommend is getting the non-working node version to make the working version. There are several ways to set the node version and there is more documentation here:

> **[Manage build dependencies](https://docs.netlify.com/configure-builds/manage-dependencies/#node-js-and-javascript)**
>
> Specify dependencies for your project so that our platform can install required languages and software before running a build.

If changing the node version doesn’t resolve this or if there are other questions, please let us know.

---

<div class="post-metadata">

**Author:** ![haigopi](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/haigopi/32/40600_2.png) [@haigopi](https://answers.netlify.com/u/haigopi)\
**Post date:** [August 25, 2022, 2:51am UTC](https://answers.netlify.com/t/same-source-code-build-failure-on-one-site-and-not-an-another-site/74129/3 "2022-08-25T02:51:05Z")

</div>

> [@luke](#):
>
> `v14.20.0`

Thank you! Updated the build version and I could able to see the same in logs  
3:29:09 PM: Downloading and installing node v14.20.0…

The issue still persists. [Netlify App](https://app.netlify.com/teams/haigopi/builds/63068a0fd46b7c000864f848)  
Something else might be going with the env! The other domain vsdevqa.netlify.app 's build is passing though.

---

<div class="post-metadata">

**Author:** ![haigopi](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/haigopi/32/40600_2.png) [@haigopi](https://answers.netlify.com/u/haigopi)\
**Post date:** [August 27, 2022, 3:32pm UTC](https://answers.netlify.com/t/same-source-code-build-failure-on-one-site-and-not-an-another-site/74129/4 "2022-08-27T15:32:52Z")

</div>

@luke Any guidance will be appreciated. As the build issue still persists.

Thanks.

---

<div class="post-metadata">

**Author:** ![coelmay](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/coelmay/32/24427_2.png) [@coelmay](https://answers.netlify.com/u/coelmay)\
**Post date:** [August 27, 2022, 9:38pm UTC](https://answers.netlify.com/t/same-source-code-build-failure-on-one-site-and-not-an-another-site/74129/5 "2022-08-27T21:38:44Z")

</div>

Hey @haigopi

Unfortunately the deploy log you shared is private. If you are able to make it public, or share the text here, the community at large could provide assistance.

---

<div class="post-metadata">

**Author:** ![haigopi](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/haigopi/32/40600_2.png) [@haigopi](https://answers.netlify.com/u/haigopi)\
**Post date:** [August 28, 2022, 5:21am UTC](https://answers.netlify.com/t/same-source-code-build-failure-on-one-site-and-not-an-another-site/74129/6 "2022-08-28T05:21:55Z")

</div>

Here is the log of the failing build. I also attached the log of the successful build of the same code on another site at the bottom.

12:07:30 AM: Build ready to start  
12:07:30 AM: ---------------------------------------------------------------------  
WARNING: Starter plan site builds from private, organization-owned GitHub repositories will fail after September 30, 2022.

This build was triggered from a private, organization-owned GitHub repository, which is now a feature of the Pro plan.  
To avoid service disruption, please upgrade your plan or change your repository settings by September 30, 2022.

## If you upgrade to Pro, you can get the first month free: For more details, including how to continue building your site on the Starter plan, visit our FAQ page:

12:07:31 AM: build-image version: d7b3dbfb0846505993c9a131894d1858074c90b4 (focal)  
12:07:31 AM: build-image tag: v4.10.1  
12:07:31 AM: buildbot version: f45292fab0b32cea549baa8489f553abb9d888be  
12:07:31 AM: Building without cache  
12:07:31 AM: Starting to prepare the repo for build  
12:07:32 AM: No cached dependencies found. Cloning fresh repo  
12:07:32 AM: git clone github-com/VantaShala/ui  
12:07:33 AM: Preparing Git Reference refs/heads/master  
12:07:34 AM: Parsing package.json dependencies  
12:07:35 AM: Starting build script  
12:07:35 AM: Installing dependencies  
12:07:35 AM: Python version set to 2.7  
12:07:35 AM: Downloading and installing node v14.19.0…  
12:07:35 AM: Downloading nodejs-org/dist/v14.19.0/node-v14.19.0-linux-x64.tar.xz…  
12:07:36 AM: Computing checksum with sha256sum  
12:07:36 AM: Checksums matched!  
12:07:37 AM: Now using node v14.19.0 (npm v6.14.16)  
12:07:38 AM: Started restoring cached build plugins  
12:07:38 AM: Finished restoring cached build plugins  
12:07:38 AM: Attempting ruby version 2.7.1, read from environment  
12:07:38 AM: Required ruby-2.7.1 is not installed - installing.  
12:07:38 AM: Searching for binary rubies, this might take some time.  
12:07:39 AM: Found remote file rvm\_io.global.ssl.fastly.net/binaries/ubuntu/20.04/x86\_64/ruby-2.7.1.tar.bz2  
12:07:39 AM: Checking requirements for ubuntu.  
12:07:39 AM: Requirements installation successful.  
12:07:39 AM: ruby-2.7.1 - #configure  
12:07:39 AM: ruby-2.7.1 - #download  
12:07:40 AM: ruby-2.7.1 - #validate archive  
12:07:43 AM: ruby-2.7.1 - #extract  
12:07:45 AM: ruby-2.7.1 - #validate binary  
12:07:45 AM: ruby-2.7.1 - #setup  
12:07:46 AM: ruby-2.7.1 - #gemset created /opt/buildhome/.rvm/gems/ruby-2.7.1 at global  
12:07:46 AM: ruby-2.7.1 - #importing gemset /opt/buildhome/.rvm/gemsets/global.gems…  
12:07:46 AM: ruby-2.7.1 - #generating global wrappers…  
12:07:46 AM: ruby-2.7.1 - #gemset created /opt/buildhome/.rvm/gems/ruby-2.7.1  
12:07:46 AM: ruby-2.7.1 - #importing gemsetfile /opt/buildhome/.rvm/gemsets/default.gems evaluated to empty gem list  
12:07:47 AM: ruby-2.7.1 - #generating default wrappers…  
12:07:47 AM: Using /opt/buildhome/.rvm/gems/ruby-2.7.1  
12:07:47 AM: Using ruby version 2.7.1  
12:07:47 AM: Using PHP version 8.0  
12:07:47 AM: No npm workspaces detected  
12:07:47 AM: Started restoring cached node modules  
12:07:47 AM: Finished restoring cached node modules  
12:07:47 AM: Installing NPM modules using NPM version 6.14.16  
12:07:51 AM: npm WARN deprecated eslint-loader at 2.2.1: This loader has been deprecated. Please use eslint-webpack-plugin  
12:07:51 AM: npm WARN deprecated axios at 0.19.2: Critical security vulnerability fixed in v0.21.1. For more information, see github-com/axios/axios/pull/3410  
12:07:53 AM: npm WARN deprecated request at 2.88.2: request has been deprecated, see github-com/request/request/issues/3142  
12:07:53 AM: npm WARN deprecated html-webpack-plugin at 3.2.0: 3.x is no longer supported  
12:07:54 AM: npm WARN deprecated at types/googlemaps at 3.43.3: Types for the Google Maps browser API have moved to at types/google.maps. Note: these types are not for the googlemaps npm package, which is a Node API.  
12:07:56 AM: npm WARN deprecated at hapi/joi at 15.1.1: Switch to ‘npm install joi’  
12:07:56 AM: npm WARN deprecated request-promise at 4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see github-com/request/request/issues/3142  
12:07:58 AM: npm WARN deprecated uuid at 3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See v8.dev/blog/math-random for details.  
12:07:59 AM: npm WARN deprecated har-validator at 5.1.5: this library is no longer supported  
12:07:59 AM: npm WARN deprecated puppeteer at 1.20.0: Version no longer supported. Upgrade to at latest  
12:08:00 AM: npm WARN deprecated chokidar at 2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies  
12:08:00 AM: npm WARN deprecated core-js at 2.6.12: core-js at \<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.  
12:08:02 AM: npm WARN deprecated at hapi/hoek at 8.5.1: This version has been deprecated and is no longer supported or maintained  
12:08:02 AM: npm WARN deprecated at hapi/bourne at 1.3.2: This version has been deprecated and is no longer supported or maintained  
12:08:02 AM: npm WARN deprecated at hapi/address at 2.1.4: Moved to ‘npm install at sideway/address’  
12:08:02 AM: npm WARN deprecated at hapi/topo at 3.1.6: This version has been deprecated and is no longer supported or maintained  
12:08:02 AM: npm WARN deprecated debug at 3.2.6: Debug versions \>=3.2.0 \<3.2.7 || \>=4 \<4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (github-com/visionmedia/debug/issues/797)  
12:08:02 AM: npm WARN deprecated mkdirp at 0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)  
12:08:03 AM: npm WARN deprecated request-promise-native at 1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see github-com/request/request/issues/3142  
12:08:06 AM: npm WARN deprecated fsevents at 1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.  
12:08:06 AM: npm WARN deprecated querystring at 0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.  
12:08:07 AM: npm WARN deprecated source-map-resolve at 0.5.3: See github-com/lydell/source-map-resolve#deprecated  
12:08:07 AM: npm WARN deprecated sane at 4.1.0: some dependency vulnerabilities fixed, support for node \< 10 dropped, and newer ECMAScript syntax/features added  
12:08:07 AM: npm WARN deprecated urix at 0.1.0: Please see github-com/lydell/urix#deprecated  
12:08:08 AM: npm WARN deprecated svgo at 1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.  
12:08:09 AM: npm WARN deprecated source-map-url at 0.4.1: See github-com/lydell/source-map-url#deprecated  
12:08:09 AM: npm WARN deprecated resolve-url at 0.2.1: github-com/lydell/resolve-url#deprecated  
12:08:09 AM: npm WARN deprecated stable at 0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: developer.mozilla-org/en-US/docs/Web/JavaScript/Reference/Global\_Objects/Array/sort#browser\_compatibility  
12:08:10 AM: npm WARN deprecated left-pad at 1.3.0: use String.prototype.padStart()  
12:08:52 AM: \> deasync at 0.1.28 install /opt/build/repo/node\_modules/deasync  
12:08:52 AM: \> node ./build.js  
12:08:52 AM: `linux-x64-node-14` exists; testing  
12:08:52 AM: Binary is fine; exiting  
12:08:53 AM: \> puppeteer at 1.20.0 install /opt/build/repo/node\_modules/puppeteer  
12:08:53 AM: \> node install.js  
12:08:56 AM: Chromium downloaded to /opt/build/repo/node\_modules/puppeteer/.local-chromium/linux-686378  
12:08:56 AM: \> yorkie at 2.0.0 install /opt/build/repo/node\_modules/yorkie  
12:08:56 AM: \> node bin/install.js  
12:08:56 AM: CI detected, skipping Git hooks installation  
12:08:56 AM: \> chromedriver at 81.0.0 install /opt/build/repo/node\_modules/chromedriver  
12:08:56 AM: \> node install.js  
12:08:57 AM: Current existing ChromeDriver binary is unavailable, proceeding with download and extraction.  
12:08:57 AM: Downloading from file: chromedriver.storage.googleapis-com/81.0.4044.69/chromedriver\_linux64.zip  
12:08:57 AM: Saving to file: /opt/buildhome/tmp/81.0.4044.69/chromedriver/chromedriver\_linux64.zip  
12:08:57 AM: Received 1040K…  
12:08:57 AM: Received 2080K…  
12:08:57 AM: Received 3120K…  
12:08:57 AM: Received 4160K…  
12:08:57 AM: Received 4840K total.  
12:08:57 AM: Extracting zip contents.  
12:08:57 AM: Copying to target path /opt/build/repo/node\_modules/chromedriver/lib/chromedriver  
12:08:57 AM: Fixing file permissions.  
12:08:57 AM: Done. ChromeDriver binary available at /opt/build/repo/node\_modules/chromedriver/lib/chromedriver/chromedriver  
12:08:57 AM: \> node-sass at 5.0.0 install /opt/build/repo/node\_modules/node-sass  
12:08:57 AM: \> node scripts/install.js  
12:08:57 AM: Downloading binary from github-com/sass/node-sass/releases/download/v5.0.0/linux-x64-83\_binding.node  
12:08:58 AM: Download complete  
12:08:58 AM: Binary saved to /opt/build/repo/node\_modules/node-sass/vendor/linux-x64-83/binding.node  
12:08:58 AM: Caching binary to /opt/buildhome/.npm/node-sass/5.0.0/linux-x64-83\_binding.node  
12:08:58 AM: \> core-js at 2.6.12 postinstall /opt/build/repo/node\_modules/babel-runtime/node\_modules/core-js  
12:08:58 AM: \> node -e “try{require(‘./postinstall’)}catch(e){}”  
12:08:58 AM: \> core-js at 3.25.0 postinstall /opt/build/repo/node\_modules/core-js  
12:08:58 AM: \> node -e “try{require(‘./postinstall’)}catch(e){}”  
12:08:58 AM: \> ejs at 2.7.4 postinstall /opt/build/repo/node\_modules/webpack-bundle-analyzer/node\_modules/ejs  
12:08:58 AM: \> node ./postinstall.js  
12:08:58 AM: \> cypress at 9.7.0 postinstall /opt/build/repo/node\_modules/cypress  
12:08:58 AM: \> node index.js --exec install  
12:08:59 AM: Note: Overriding Cypress cache directory to: ./node\_modules/.cache/CypressBinary  
12:08:59 AM: Previous installs of Cypress may not be found.  
12:08:59 AM: Installing Cypress (version: 9.7.0)  
12:08:59 AM: [STARTED] Task without title.  
12:09:00 AM: [SUCCESS] Task without title.  
12:09:00 AM: [STARTED] Task without title.  
12:09:06 AM: [SUCCESS] Task without title.  
12:09:06 AM: [STARTED] Task without title.  
12:09:06 AM: [SUCCESS] Task without title.  
12:09:07 AM: You can now open Cypress by running: node\_modules/.bin/cypress open  
12:09:07 AM: on.cypress-io/installing-cypress  
12:09:07 AM: \> geckodriver at 1.22.3 postinstall /opt/build/repo/node\_modules/geckodriver  
12:09:07 AM: \> node index.js  
12:09:07 AM: Downloading geckodriver… Extracting… Complete.  
12:09:07 AM: \> node-sass at 5.0.0 postinstall /opt/build/repo/node\_modules/node-sass  
12:09:07 AM: \> node scripts/build.js  
12:09:07 AM: Binary found at /opt/build/repo/node\_modules/node-sass/vendor/linux-x64-83/binding.node  
12:09:07 AM: Testing binary  
12:09:07 AM: Binary is fine  
12:09:07 AM: \> vuex-module-decorators at 1.2.0 postinstall /opt/build/repo/node\_modules/vuex-module-decorators  
12:09:07 AM: \> node -e “try{require(‘./postinstall’)}catch(e){}”  
12:09:09 AM: npm notice created a lockfile as package-lock.json. You should commit this file.  
12:09:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents at ~2.3.2 (node\_modules/chokidar/node\_modules/fsevents):  
12:09:09 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents at 2.3.2: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})  
12:09:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents at ^1.2.7 (node\_modules/watchpack-chokidar2/node\_modules/chokidar/node\_modules/fsevents):  
12:09:09 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents at 1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})  
12:09:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents at ^1.2.7 (node\_modules/jest-haste-map/node\_modules/fsevents):  
12:09:09 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents at 1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})  
12:09:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents at ^1.2.7 (node\_modules/webpack-dev-server/node\_modules/chokidar/node\_modules/fsevents):  
12:09:09 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents at 1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})  
12:09:09 AM: added 2376 packages from 1554 contributors and audited 2383 packages in 81.387s  
12:09:10 AM: 133 packages are looking for funding  
12:09:10 AM: run `npm fund` for details  
12:09:10 AM: found 39 vulnerabilities (2 low, 13 moderate, 23 high, 1 critical)  
12:09:10 AM: run `npm audit fix` to fix them, or `npm audit` for details  
12:09:10 AM: NPM modules installed  
12:09:10 AM: Started restoring cached go cache  
12:09:10 AM: Finished restoring cached go cache  
12:09:10 AM: Installing Go version 1.14.4 (requested 1.14.4)  
12:09:14 AM: unset GOOS;  
12:09:14 AM: unset GOARCH;  
12:09:14 AM: export GOROOT=‘/opt/buildhome/.gimme/versions/go1.14.4.linux.amd64’;  
12:09:14 AM: export PATH="/opt/buildhome/.gimme/versions/go1.14.4.linux.amd64/bin:{PATH}"; 12:09:14 AM: go version \>&2; 12:09:14 AM: export GIMME\_ENV="/opt/buildhome/.gimme/env/go1.14.4.linux.amd64.env" 12:09:14 AM: go version go1.14.4 linux/amd64 12:09:14 AM: Installing missing commands 12:09:14 AM: Verify run directory 12:09:15 AM: ​ 12:09:15 AM: ──────────────────────────────────────────────────────────────── 12:09:15 AM: Netlify Build 12:09:15 AM: ──────────────────────────────────────────────────────────────── 12:09:15 AM: ​ 12:09:15 AM: ❯ Version 12:09:15 AM: at netlify/build 27.15.7 12:09:15 AM: ​ 12:09:15 AM: ❯ Flags 12:09:15 AM: baseRelDir: true 12:09:15 AM: buildId: 630af812fe01ec01eb7ac8f2 12:09:15 AM: deployId: 630af812fe01ec01eb7ac8f4 12:09:15 AM: ​ 12:09:15 AM: ❯ Current directory 12:09:15 AM: /opt/build/repo 12:09:15 AM: ​ 12:09:15 AM: ❯ Config file 12:09:15 AM: No config file was defined: using default values. 12:09:15 AM: ​ 12:09:15 AM: ❯ Context 12:09:15 AM: production 12:09:15 AM: ​ 12:09:15 AM: ──────────────────────────────────────────────────────────────── 12:09:15 AM: 1. Build command from Netlify app 12:09:15 AM: ──────────────────────────────────────────────────────────────── 12:09:15 AM: ​ 12:09:15 AM: npm run build  
12:09:15 AM: \> vantashala at 0.1.0 build /opt/build/repo  
12:09:15 AM: \> vue-cli-service build  
12:09:16 AM: - Building for production…  
12:09:16 AM: Starting type checking service…  
12:09:16 AM: Using 1 worker with 2048MB memory limit  
12:09:32 AM: [BABEL] Note: The code generator has deoptimised the styling of /opt/build/repo/node\_modules/vuetify/dist/vuetify.js as it exceeds the max of 500KB.  
12:09:37 AM: DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.  
12:09:37 AM: Recommendation: math.div($border-radius-root, 2) or calc($border-radius-root / 2)  
12:09:37 AM: More info and automated migrator: sass-lang-com/d/slash-div  
12:09:37 AM: ╷  
12:09:37 AM: 14 │ ‘sm’: $border-radius-root / 2,  
12:09:37 AM: │ ^^^^^^^^^^^^^^^^^^^^^^^  
12:09:37 AM: ╵  
12:09:37 AM: node\_modules/vuetify/src/styles/settings/\_variables.scss 14:11 at import  
12:09:37 AM: node\_modules/vuetify/src/styles/settings/\_index.sass 1:9 at import  
12:09:37 AM: node\_modules/vuetify/src/styles/styles.sass 2:9 at import  
12:09:37 AM: stdin 2:9 root stylesheet  
12:09:37 AM: DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.  
12:09:37 AM: Recommendation: math.div($border-radius-root, 2) or calc($border-radius-root / 2)  
12:09:37 AM: More info and automated migrator: sass-lang-com/d/slash-div  
12:09:37 AM: ╷  
12:09:37 AM: 14 │ ‘sm’: $border-radius-root / 2,  
12:09:37 AM: │ ^^^^^^^^^^^^^^^^^^^^^^^  
12:09:37 AM: ╵  
12:09:37 AM: node\_modules/vuetify/src/styles/settings/\_variables.scss 14:11 at import  
12:09:37 AM: node\_modules/vuetify/src/styles/settings/\_index.sass 1:9 at import  
12:09:37 AM: node\_modules/vuetify/src/styles/styles.sass 2:9 at import  
12:09:37 AM: stdin 2:9 root stylesheet  
12:09:37 AM: DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.  
12:09:37 AM: Recommendation: math.div($grid-gutter, 2) or calc($grid-gutter / 2)  
12:09:37 AM: More info and automated migrator: sass-lang-com/d/slash-div  
12:09:37 AM: ╷  
12:09:37 AM: 57 │ $container-padding-x: $grid-gutter / 2 !default;  
12:09:37 AM: │ ^^^^^^^^^^^^^^^^  
12:09:37 AM: ╵  
12:09:37 AM: node\_modules/vuetify/src/styles/settings/\_variables.scss 57:23 at import  
12:09:37 AM: node\_modules/vuetify/src/styles/settings/\_index.sass 1:9 at import  
12:09:37 AM: node\_modules/vuetify/src/styles/styles.sass 2:9 at import  
12:09:37 AM: stdin 2:9 root stylesheet  
12:09:37 AM: DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.  
12:11:47 AM: DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.  
12:11:47 AM: Recommendation: math.div($grid-gutter, 3) or calc($grid-gutter / 3)  
12:11:47 AM: More info and automated migrator: sass-lang-com/d/slash-div  
12:11:47 AM: ╷  
12:11:47 AM: 64 │ ‘md’: $grid-gutter / 3,  
12:11:48 AM: │ ^^^^^^^^^^^^^^^^  
12:11:48 AM: ╵  
12:11:48 AM: node\_modules/vuetify/src/styles/settings/\_variables.scss 64:11 at import  
12:11:48 AM: node\_modules/vuetify/src/styles/settings/\_index.sass 1:9 at import  
12:11:48 AM: node\_modules/vuetify/src/styles/styles.sass 2:9 at import  
12:11:48 AM: stdin 2:9 root stylesheet  
12:11:48 AM: WARNING: 1 repetitive deprecation warnings omitted.  
12:11:48 AM: WARNING: 1 repetitive deprecation warnings omitted.  
12:11:48 AM: DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.  
12:11:48 AM: Recommendation: math.div($border-radius-root, 2) or calc($border-radius-root / 2)  
12:11:48 AM: More info and automated migrator: sass-lang-com/d/slash-div  
12:11:48 AM: ╷  
12:11:48 AM: 14 │ ‘sm’: $border-radius-root / 2,  
12:11:48 AM: │ ^^^^^^^^^^^^^^^^^^^^^^^  
12:11:48 AM: ╵  
12:11:48 AM: node\_modules/vuetify/src/styles/settings/\_variables.scss 14:11 at import  
12:11:48 AM: node\_modules/vuetify/src/styles/settings/\_index.sass 1:9 at import  
12:11:48 AM: node\_modules/vuetify/src/styles/styles.sass 2:9 at import  
12:11:48 AM: stdin 2:9 root stylesheet  
12:11:48 AM: DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.  
12:11:48 AM: Recommendation: math.div($grid-gutter, 2) or calc($grid-gutter / 2)  
12:11:48 AM: More info and automated migrator: sass-lang-com/d/slash-div  
12:11:48 AM: ╷  
12:11:48 AM: 57 │ $container-padding-x: $grid-gutter / 2 !default;  
12:11:48 AM: │ ^^^^^^^^^^^^^^^^  
12:11:48 AM: ╵  
12:11:49 AM: node\_modules/vuetify/src/styles/settings/\_variables.scss 57:23 at import  
12:11:49 AM: node\_modules/vuetify/src/styles/settings/\_index.sass 1:9 at import  
12:11:49 AM: node\_modules/vuetify/src/styles/styles.sass 2:9 at import  
12:11:49 AM: stdin 2:9 root stylesheet  
12:11:49 AM: DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.  
12:11:49 AM: Recommendation: math.div($grid-gutter, 12) npm ERR! code ELIFECYCLE  
12:11:49 AM: npm ERR! errno 1  
12:11:49 AM: npm ERR! vantashala at 0.1.0 build: `vue-cli-service build`  
12:11:49 AM: npm ERR! Exit status 1  
12:11:49 AM: npm ERR!  
12:11:49 AM: npm ERR! Failed at the vantashala at 0.1.0 build script.  
12:11:49 AM: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.  
12:11:49 AM: npm ERR! A complete log of this run can be found in:  
12:11:49 AM: npm ERR! /opt/buildhome/.npm/\_logs/2022-08-28T05\_11\_08\_745Z-debug.log  
12:11:49 AM: ​  
12:11:49 AM: ────────────────────────────────────────────────────────────────  
12:11:49 AM: “build-command” failed  
12:11:49 AM: ────────────────────────────────────────────────────────────────  
12:11:49 AM: ​  
12:11:49 AM: Error message  
12:11:49 AM: Command failed with exit code 1: npm run build (ntl.fyi/exit-code-1)  
12:11:49 AM: ​  
12:11:49 AM: Error location  
12:11:49 AM: In Build command from Netlify app:  
12:11:49 AM: npm run build  
12:11:49 AM: ​  
12:11:50 AM: Resolved config  
12:11:50 AM: build:  
12:11:50 AM: command: npm run build  
12:11:50 AM: commandOrigin: ui  
12:11:50 AM: environment:  
12:11:50 AM: - NODE\_VERSION  
12:11:50 AM: publish: /opt/build/repo/dist  
12:11:50 AM: publishOrigin: ui  
12:11:50 AM: Caching artifacts  
12:11:50 AM: Started saving node modules  
12:11:50 AM: Finished saving node modules  
12:11:50 AM: Started saving build plugins  
12:11:50 AM: Finished saving build plugins  
12:11:50 AM: Started saving pip cache  
12:11:50 AM: Finished saving pip cache  
12:11:50 AM: Started saving emacs cask dependencies  
12:11:50 AM: Finished saving emacs cask dependencies  
12:11:50 AM: Started saving maven dependencies  
12:11:50 AM: Finished saving maven dependencies  
12:11:50 AM: Started saving boot dependencies  
12:11:50 AM: Finished saving boot dependencies  
12:11:50 AM: Started saving rust rustup cache  
12:11:50 AM: Finished saving rust rustup cache  
12:11:50 AM: Started saving go dependencies  
12:11:50 AM: Finished saving go dependencies  
12:11:50 AM: Cached ruby version 2.7.1  
12:11:51 AM: Build failed due to a user error: Build script returned non-zero exit code: 2  
12:11:51 AM: Failing build: Failed to build site  
12:11:51 AM: Finished processing build request in 4m19.716624352s

> Blockquote  
> Success build log:

3:21:00 PM: Build ready to start  
3:21:01 PM: build-image version: d7b3dbfb0846505993c9a131894d1858074c90b4 (focal)  
3:21:01 PM: build-image tag: v4.10.1  
3:21:01 PM: buildbot version: f7070267d9348624fde5c2d682aa32cc686742a6  
3:21:01 PM: Fetching cached dependencies  
3:21:01 PM: Starting to download cache of 631.4MB  
3:21:07 PM: Finished downloading cache in 6.148548321s  
3:21:07 PM: Starting to extract cache  
3:21:13 PM: Finished extracting cache in 5.913167427s  
3:21:13 PM: Finished fetching cache in 12.155881113s  
3:21:13 PM: Starting to prepare the repo for build  
3:21:14 PM: Preparing Git Reference refs/heads/devqa  
3:21:15 PM: Parsing package.json dependencies  
3:21:16 PM: Starting build script  
3:21:16 PM: Installing dependencies  
3:21:16 PM: Python version set to 2.7  
3:21:16 PM: Started restoring cached node version  
3:21:17 PM: Finished restoring cached node version  
3:21:18 PM: v14.20.0 is already installed.  
3:21:18 PM: Now using node v14.20.0 (npm v6.14.17)  
3:21:18 PM: Started restoring cached build plugins  
3:21:18 PM: Finished restoring cached build plugins  
3:21:18 PM: Attempting ruby version 2.7.2, read from environment  
3:21:18 PM: Using ruby version 2.7.2  
3:21:19 PM: Using PHP version 8.0  
3:21:19 PM: No npm workspaces detected  
3:21:19 PM: Started restoring cached node modules  
3:21:19 PM: Finished restoring cached node modules  
3:21:19 PM: Started restoring cached go cache  
3:21:19 PM: Finished restoring cached go cache  
3:21:19 PM: Installing Go version 1.16.5 (requested 1.16.5)  
3:21:23 PM: unset GOOS;  
3:21:23 PM: unset GOARCH;  
3:21:23 PM: export GOROOT=‘/opt/buildhome/.gimme/versions/go1.16.5.linux.amd64’;  
3:21:23 PM: export PATH="/opt/buildhome/.gimme/versions/go1.16.5.linux.amd64/bin:{PATH}"; 3:21:23 PM: go version \>&2; 3:21:23 PM: export GIMME\_ENV="/opt/buildhome/.gimme/env/go1.16.5.linux.amd64.env" 3:21:23 PM: go version go1.16.5 linux/amd64 3:21:23 PM: Installing missing commands 3:21:23 PM: Verify run directory 3:21:24 PM: ​ 3:21:24 PM: ──────────────────────────────────────────────────────────────── 3:21:24 PM: Netlify Build 3:21:24 PM: ──────────────────────────────────────────────────────────────── 3:21:24 PM: ​ 3:21:24 PM: ❯ Version 3:21:24 PM: at netlify/build 27.15.7 3:21:24 PM: ​ 3:21:24 PM: ❯ Flags 3:21:24 PM: baseRelDir: true 3:21:24 PM: buildId: 6306882b7880df0008949544 3:21:24 PM: deployId: 6306882b7880df0008949546 3:21:24 PM: ​ 3:21:24 PM: ❯ Current directory 3:21:24 PM: /opt/build/repo 3:21:24 PM: ​ 3:21:24 PM: ❯ Config file 3:21:24 PM: No config file was defined: using default values. 3:21:24 PM: ​ 3:21:24 PM: ❯ Context 3:21:24 PM: production 3:21:24 PM: ​ 3:21:24 PM: ──────────────────────────────────────────────────────────────── 3:21:24 PM: 1. Build command from Netlify app 3:21:24 PM: ──────────────────────────────────────────────────────────────── 3:21:24 PM: ​ 3:21:24 PM: npm run devbuild  
3:21:24 PM: \> vantashala at 0.1.0 devbuild /opt/build/repo  
3:21:24 PM: \> vue-cli-service build --mode devqa  
3:21:25 PM: - Building for devqa…  
3:21:26 PM: Starting type checking service…  
3:21:26 PM: Using 1 worker with 2048MB memory limit  
3:21:35 PM: [BABEL] Note: The code generator has deoptimised the styling of /opt/build/repo/node\_modules/vuetify/dist/vuetify.js as it exceeds the max of 500KB.  
3:21:52 PM: DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.  
3:21:52 PM: Recommendation: math.div($border-radius-root, 2) or calc($border-radius-root / 2)  
3:21:52 PM: More info and automated migrator: sass-lang-com/d/slash-div  
3:21:52 PM: ╷  
3:21:52 PM: 14 │ ‘sm’: $border-radius-root / 2,  
3:21:52 PM: │ ^^^^^^^^^^^^^^^^^^^^^^^  
3:21:52 PM: ╵  
3:21:52 PM: node\_modules/vuetify/src/styles/settings/\_variables.scss 14:11 at import  
3:21:52 PM: node\_modules/vuetify/src/styles/settings/\_index.sass 1:9 at import  
3:21:52 PM: node\_modules/vuetify/src/styles/styles.sass 2:9 at import  
3:21:52 PM: stdin 2:9  
3:26:21 PM: Recommendation: math.div($grid-gutter, 3) or calc($grid-gutter / 3)  
3:26:21 PM: More info and automated migrator: sass-lang-com/d/slash-div  
3:26:21 PM: ╷  
3:26:21 PM: 64 │ ‘md’: $grid-gutter / 3,  
3:26:21 PM: │ ^^^^^^^^^^^^^^^^  
3:26:21 PM: ╵  
3:26:21 PM: node\_modules/vuetify/src/styles/settings/\_variables.scss 64:11 at import  
3:26:21 PM: node\_modules/vuetify/src/styles/settings/\_index.sass 1:9 at import  
3:26:21 PM: node\_modules/vuetify/src/styles/styles.sass 2:9 at import  
3:26:21 PM: stdin 2:9 root stylesheet  
3:26:21 PM: DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.  
3:26:22 PM: Recommendation: math.div($grid-gutter, 3) or calc($grid-gutter / 3)  
3:26:22 PM: More info and automated migrator: sass-lang-com/d/slash-div  
3:26:22 PM: ╷  
3:26:22 PM: 64 │ ‘md’: $grid-gutter / 3,  
3:26:22 PM: │ ^^^^^^^^^^^^^^^^  
3:26:22 PM: ╵  
3:26:22 PM: node\_modules/vuetify/src/styles/settings/\_variables.scss 64:11 at import  
3:26:22 PM: node\_modules/vuetify/src/styles/settings/\_index.sass 1:9 at import  
3:26:22 PM: node\_modules/vuetify/src/styles/styles.sass 2:9 at import  
3:26:22 PM: stdin 2:9 root stylesheet  
3:26:22 PM: WARNING: 1 repetitive deprecation warnings omitted.  
3:26:22 PM: WARNING: 1 repetitive deprecation warnings omitted.  
3:26:22 PM: WARNING: 1 repetitive deprecation warnings omitted.  
3:26:22 PM: WARNING: 1 repetitive deprecation warnings omitted.  
3:26:22 PM: WARNING: 1 repetitive deprecation warnings omitted.  
3:26:22 PM: WARNING: 1 repetitive deprecation warnings omitted.  
3:26:22 PM: WARNING: 1 repetitive deprecation warnings omitted.  
3:26:22 PM: WARNING: 1 repetitive deprecation warnings omitted.  
3:26:22 PM: WARNING: 4 repetitive deprecation warnings omitted.  
3:26:22 PM: WARNING: 3 repetitive deprecation warnings omitted.  
3:26:22 PM: WARNING: 2 repetitive deprecation warnings omitted.  
3:26:22 PM: WARNING: 2 repetitive deprecation warnings omitted.  
3:26:22 PM: WARNING: 2 repetitive deprecation warnings omitted.  
3:26:22 PM: WARNING: 2 repetitive deprecation warnings omitted.  
3:26:22 PM: WARNING: 2 repetitive deprecation warnings omitted.  
3:26:22 PM: ​  
3:26:23 PM: (build-command completed in 3m 59.4s)  
3:26:23 PM: ​  
3:26:23 PM: ────────────────────────────────────────────────────────────────  
3:26:23 PM: 2. Deploy site  
3:26:23 PM: ────────────────────────────────────────────────────────────────  
3:26:23 PM: ​  
3:26:23 PM: Site deploy was successfully initiated  
3:26:23 PM: ​  
3:26:23 PM: (Deploy site completed in 1.3s)  
3:26:23 PM: ​  
3:26:23 PM: ────────────────────────────────────────────────────────────────  
3:26:23 PM: Netlify Build Complete  
3:26:23 PM: ────────────────────────────────────────────────────────────────  
3:26:23 PM: ​  
3:26:23 PM: (Netlify Build completed in 4m 0.8s)  
3:26:23 PM: Caching artifacts  
3:26:23 PM: Started saving node modules  
3:26:23 PM: Finished saving node modules  
3:26:23 PM: Started saving build plugins  
3:26:23 PM: Finished saving build plugins  
3:26:23 PM: Started saving pip cache  
3:26:23 PM: Finished saving pip cache  
3:26:23 PM: Started saving emacs cask dependencies  
3:26:23 PM: Finished saving emacs cask dependencies  
3:26:23 PM: Started saving maven dependencies  
3:26:24 PM: Finished saving maven dependencies  
3:26:24 PM: Started saving boot dependencies  
3:26:24 PM: Finished saving boot dependencies  
3:26:24 PM: Started saving rust rustup cache  
3:26:24 PM: Finished saving rust rustup cache  
3:26:24 PM: Started saving go dependencies  
3:26:24 PM: Finished saving go dependencies  
3:26:24 PM: Build script success  
3:26:43 PM: Uploading Cache of size 632.6MB  
3:26:48 PM: Finished processing build request in 5m46.784691022s

---

<div class="post-metadata">

**Author:** ![coelmay](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/coelmay/32/24427_2.png) [@coelmay](https://answers.netlify.com/u/coelmay)\
**Post date:** [August 28, 2022, 5:36am UTC](https://answers.netlify.com/t/same-source-code-build-failure-on-one-site-and-not-an-another-site/74129/7 "2022-08-28T05:36:38Z")

</div>

Hey @haigopi

There is a different NodeJS version used on the failing

> [@haigopi](#):
>
> 12:07:37 AM: Now using node v14.19.0 (npm v6.14.16)

and the successful

> [@haigopi](#):
>
> 3:21:18 PM: Now using node v14.20.0 (npm v6.14.17)

Perhaps more importantly, is the build command.  
On the failing I see

> [@haigopi](#):
>
> 12:09:15 AM: $ npm run build  
> 12:09:15 AM: \> vantashala at 0.1.0 build /opt/build/repo  
> 12:09:15 AM: \> vue-cli-service build

vs the successful

> [@haigopi](#):
>
> 3:21:24 PM: $ npm run devbuild  
> 3:21:24 PM: \> vantashala at 0.1.0 devbuild /opt/build/repo  
> 3:21:24 PM: \> vue-cli-service build --mode devqa

In the successful one, you are specifying a specific mode, a _development_ mode I presume. In the failing one, no mode is specified, but possibly it is using _production_, this the deprecation warnings are causing the build to fail.

---

<div class="post-metadata">

**Author:** ![haigopi](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/haigopi/32/40600_2.png) [@haigopi](https://answers.netlify.com/u/haigopi)\
**Post date:** [August 29, 2022, 5:33am UTC](https://answers.netlify.com/t/same-source-code-build-failure-on-one-site-and-not-an-another-site/74129/8 "2022-08-29T05:33:34Z")

</div>

First, Thank you for your time to look into this.

1. You are right, mode “devqa” supplies the environment-specific URLs that this app is required to connect. The default is production.
2. I just tried if the version is the problem. But I tried both node versions and both of them failed.
3. “the deprecation warnings” → This is a VUE JS + Vuetify App version 2.0+. Both sites have these warnings while one is successful and the other is not. Also, these warnings never caused the builds to fail in the last two years. I am guessing something somewhere is wrong after the ubuntu version update. Builds are failing after this environment upgrade I believe. I may be wrong as I updated the same for the other site as well. My local build is successful with the same node version.

---

<div class="post-metadata">

**Author:** ![haigopi](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/haigopi/32/40600_2.png) [@haigopi](https://answers.netlify.com/u/haigopi)\
**Post date:** [August 29, 2022, 5:55am UTC](https://answers.netlify.com/t/same-source-code-build-failure-on-one-site-and-not-an-another-site/74129/9 "2022-08-29T05:55:56Z")

</div>

I just cleared the cache and re-ran the build for the site which used to be Successful. Now, I see that build is failing as well. So, it might be some npm package causing the error, which is hard to figure out for me.

---

<div class="post-metadata">

**Author:** ![coelmay](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/coelmay/32/24427_2.png) [@coelmay](https://answers.netlify.com/u/coelmay)\
**Post date:** [August 29, 2022, 6:14am UTC](https://answers.netlify.com/t/same-source-code-build-failure-on-one-site-and-not-an-another-site/74129/10 "2022-08-29T06:14:39Z")

</div>

I was going to make that suggesting. Looking at the build logs, `vuetify` is a possibility

> [@haigopi](#):
>
> node\_modules/vuetify/src/styles/settings/\_variables.scss 14:11 at import

or `sass`

> [@haigopi](#):
>
> DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.  
> 12:11:48 AM: Recommendation: math.div($border-radius-root, 2) or calc($border-radius-root / 2)  
> 12:11:48 AM: More info and automated migrator: sass-lang-com/d/slash-div

see: [sass-lang-com/d/slash-div](https://sass-lang.com/d/slash-div)

If the build it working locally, you might want to pin the version of `sass`, or whatever package (possibly `vuetify`) that uses it.
