Error in deploy with build image v3.13.0 for gatsby site

Support
,
1

Hello, i have a build problem with the last image: v3.13.0
With the previous image: v3.11.0 is ok, but, with the last image: v3.13.0, error build.
Many thanks

Site name:
zangolotinosclublectura

Error log resume:

6:54:00 PM: Build ready to start
6:54:02 PM: build-image version: ac716c5be7f79fe384a0f3759e8ef612cb821a37 (xenial)
6:54:02 PM: build-image tag: v3.13.0

6:56:42 PM: Netlify Build
6:56:42 PM: ────────────────────────────────────────────────────────────────
6:56:42 PM: ​
6:56:42 PM: ❯ Version
6:56:42 PM: @netlify/build 27.0.1
6:56:42 PM: ​
6:56:42 PM: ❯ Flags
6:56:42 PM: baseRelDir: false
6:56:42 PM: buildId: 6262dda8a2e71509b0498278
6:56:42 PM: deployId: 6262dda8a2e71509b049827a
6:56:42 PM: ​
6:56:42 PM: ❯ Current directory
6:56:42 PM: /opt/build/repo
6:56:42 PM: ​
6:56:42 PM: ❯ Config file
6:56:42 PM: No config file was defined: using default values.
6:56:42 PM: ​
6:56:42 PM: ❯ Context
6:56:42 PM: production
6:56:42 PM: ​

6:57:37 PM: gatsby build
6:57:37 PM: Build a Gatsby project.
6:57:37 PM: Options:
6:57:37 PM: --verbose Turn on verbose output [boolean] [default: false]
6:57:37 PM: --no-color Turn off the color in output [boolean] [default: false]
6:57:37 PM: --prefix-paths Build site with link paths prefixed (set prefix in your config). [boolean] [default: false]
6:57:37 PM: --no-uglify Build site without uglifying JS bundles (for debugging). [boolean] [default: false]
6:57:37 PM: -h, --help Show help [boolean]
6:57:37 PM: -v, --version Show version number [boolean]
6:57:37 PM: error There was a problem loading the local build command. Gatsby may not be installed. Perhaps you need to run “npm install”?
6:57:37 PM:
6:57:37 PM: Error: evalmachine.:1
6:57:37 PM: Object.getOwnPropertyNames(globalThis)
6:57:37 PM: ^
6:57:37 PM: ReferenceError: globalThis is not defined
6:57:37 PM:

4

Hi @rccclr,

I think this may have to do with the fact there’s a pinned software version associated with your build as mentioned here:

Here’s another article that talks about the dependency cache:

Hopefully these articles can get you pointed in the right direction. If nothing else, have you tried redeploying with a cleared cache? That might be worth a shot:

Screen Shot 2022-04-25 at 4.14.21 PM

  • Elden
1 Like
5

Hello Elden

We have a blog on Github associated with the site based on Gatsby, for about 4 years.

The only changes we make is: add markdown files and images, and it’s working very well for us.

However, now when performing “deploy” or “clear cache and deploy”, the result is the same, the attached error.

I have compared the deploy logs, from the latest version of the site with the latest deploy, and the fundamental difference is: v3.11.0 is ok, but, with the last image: v3.13.0, error build.

I understand that it is some configuration that you have modified.

Is it possible to use the previous version v3.11.0 when deploying or how can I solve it?

Thank you very much for your help

6

Hi @rccclr,

You should be able to specify the version of Gatsby to use in your package.json file and that will make the deploy use that version when building your site. I hope that helps.

Elden

7

@rccclr

One thing to mention as well – it was pointed out to me that Gatsby 3.11.0 is getting a little old so pinning that version might work for now but not for the long run. You might consider upgrading to version 4 of Gatsby as well in order to troubleshoot this issue.

Elden

8

Hello Elden

Sorry for the confusion:

1.- When I refer to versions 3.11.0 and 3.13.0 they are the versions of your deploy images, they appear in the deploy logs.

Is it possible to indicate in the deploy that it uses version 3.11.0?

2.- My github repository “I haven’t modified it for about 3 years” and it has been working fine, on Netlify, until now. You can see in the above logs, and the only change between those versions are md files and images, we haven’t changed any version of the software.

I think there is a problem in the changes you have made in version 3.13.0 (see attached deploy logs), with respect to version 3.11.0 that affects our site.

If you could please review it and tell me what I can do? I would appreciate it.

Many thanks.

9

hey @rccclr , could you share your current package.json file please so we can take a look? thanks!

10

Hello Perry, this is the content of “package.json”. Many thanks

{
“name”: “gatsby-starter-personal-blog”,
“description”: “A Gatsby starter for a personal blog”,
“author”: “Greg Lobinski greglobinski@gmail.com”,
“repository”: “GitHub - greglobinski/gatsby-starter-personal-blog: A ready to use, easy to customize, fully equipped GatsbyJS blog starter with 'like app' layout and views transitions.”,
“version”: “1.1.1”,
“license”: “MIT”,
“scripts”: {
“develop”: “gatsby develop”,
“develop-host”: “gatsby develop --host 192.168.0.112”,
“build”: “gatsby build”,
“serve”: “gatsby serve”,
“format-output”: “prettier src//*.{js,jsx}",
“format”: "prettier --write src//.{js,jsx}",
“lint-errors”: "eslint src/**/.{js,jsx} --quiet”,
“lint”: “eslint src/**/*.{js,jsx}”,
“generate-app-icons”: “sh ./scripts/generate-app-icons.sh”
},
“devDependencies”: {
“babel-eslint”: “^8.2.6”,
“babel-plugin-dynamic-import-webpack”: “^1.0.2”,
“babel-plugin-syntax-dynamic-import”: “^6.18.0”,
“dotenv”: “^6.0.0”,
“eslint”: “^5.1.0”,
“eslint-config-google”: “^0.9.1”,
“eslint-config-prettier”: “^2.9.0”,
“eslint-plugin-graphql”: “^2.1.1”,
“eslint-plugin-import”: “^2.13.0”,
“eslint-plugin-jsx-a11y”: “^6.1.1”,
“eslint-plugin-prettier”: “^2.6.2”,
“eslint-plugin-react”: “^7.10.0”,
“prettier”: “^1.13.7”,
“sharp-cli”: “^1.7.0”,
“webpack-bundle-analyzer”: “^2.13.1”
},
“dependencies”: {
“@material-ui/core”: “^1.4.0”,
“@material-ui/icons”: “^1.1.0”,
“color”: “^3.0.0”,
“gatsby”: “^1.9.274”,
“gatsby-cli”: “^2.7.13”,
“gatsby-image”: “^1.0.55”,
“gatsby-link”: “^1.6.46”,
“gatsby-plugin-algolia”: “^0.0.4”,
“gatsby-plugin-catch-links”: “^1.0.24”,
“gatsby-plugin-feed”: “^1.3.25”,
“gatsby-plugin-google-analytics”: “^1.0.31”,
“gatsby-plugin-jss”: “^1.5.14”,
“gatsby-plugin-manifest”: “^1.0.27”,
“gatsby-plugin-netlify”: “^1.0.21”,
“gatsby-plugin-offline”: “^1.0.18”,
“gatsby-plugin-react-helmet”: “^2.0.11”,
“gatsby-plugin-react-next”: “^1.0.11”,
“gatsby-plugin-react-svg”: “^1.1.1”,
“gatsby-plugin-sharp”: “^1.6.48”,
“gatsby-plugin-sitemap”: “^1.2.25”,
“gatsby-remark-component”: “^1.1.3”,
“gatsby-remark-copy-linked-files”: “^1.5.37”,
“gatsby-remark-external-links”: “^0.0.4”,
“gatsby-remark-images”: “^1.5.67”,
“gatsby-remark-prismjs”: “^2.0.5”,
“gatsby-remark-responsive-iframe”: “^1.4.20”,
“gatsby-remark-smartypants”: “^1.4.10”,
“gatsby-source-filesystem”: “^1.5.39”,
“gatsby-transformer-remark”: “^1.7.44”,
“gatsby-transformer-sharp”: “^1.6.27”,
“hoek”: “^5.0.3”,
“instantsearch.css”: “^7.1.0”,
“libvips”: “0.0.2”,
“prismjs”: “^1.15.0”,
“react-custom-scrollbars”: “^4.2.1”,
“react-facebook”: “^5.0.3”,
“react-headroom”: “^2.2.2”,
“react-helmet”: “^5.1.3”,
“react-instantsearch”: “^5.2.2”,
“react-lazyload”: “^2.3.0”,
“react-loadable-visibility”: “^2.5.0”,
“react-material-ui-form-validator”: “^2.0.1”,
“react-obfuscate”: “^2.1.4”,
“react-popper”: “0.10.4”,
“react-redux”: “^5.0.6”,
“react-share”: “^2.2.0”,
“rebound”: “^0.1.0”,
“redux”: “^4.0.0”,
“redux-devtools-extension”: “^2.13.5”,
“screenfull”: “^3.3.2”,
“sharp”: “^0.22.1”
}
}

12

Hey there, @rccclr :wave:

Thanks so much for reaching out! We have taken a look, and we believe you are encountering issues due to a few components of your site being out of date. I know this isn’t the news you were looking for, as you said it was working previously, but we do believe that running some upgrades will be necessary here.

I think starting by upgrading your node version from 10 will be a good start. That version has reached its end of life and Node 12 might reach there any time soon. Once you upgrade to at least Node 14, you can probably see additional breaking errors, but it’s a change that would be needed at this stage. You can set your node version in an .nvmrc file, Here is some more information for you: GitHub - nvm-sh/nvm: Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions

Let us know how this goes for you!

13

Hello Hillary, many thanks for your support.

  1. I create the file “.nvmrc” in my site.
  2. In the “last_deploy_ok.log” get the node version ok, it is: 10.24.1 and put this value in the file “.nvmrc”.
  3. I new deploy with this change and the new version show: 10.24.1, but, the error is the same.
    For deploy this site, its possible select the your version build image “v3.11.0” (ok for my site) and not “v3.13.0” (error in my site)?

Many thanks

last_deploy_ok.log

12:29:37 AM: Build ready to start
12:29:39 AM: build-image version: 01acd77a1510fdb8f4fc9a04f21fc94be8fc1167 (xenial)
12:29:39 AM: build-image tag: v3.11.0
12:29:39 AM: buildbot version: 4ac77ee15240cafa5a14a04b6ca18d8959fa98e6
12:29:39 AM: Fetching cached dependencies
12:29:39 AM: Starting to download cache of 484.3MB
12:29:45 AM: Finished downloading cache in 6.498353604s
12:29:45 AM: Starting to extract cache
12:29:57 AM: Finished extracting cache in 11.541128696s
12:29:57 AM: Finished fetching cache in 18.104210453s
12:29:57 AM: Starting to prepare the repo for build
12:29:57 AM: Preparing Git Reference refs/heads/master
12:29:58 AM: Parsing package.json dependencies
12:29:59 AM: Starting build script
12:29:59 AM: Installing dependencies
12:29:59 AM: Python version set to 2.7
12:29:59 AM: Started restoring cached node version
12:30:01 AM: Finished restoring cached node version
12:30:02 AM: v10.24.1 is already installed.
12:30:03 AM: Now using node v10.24.1 (npm v6.14.12)
12:30:03 AM: Started restoring cached build plugins
12:30:03 AM: Finished restoring cached build plugins
12:30:03 AM: Attempting ruby version 2.6.2, read from environment
12:30:04 AM: Using ruby version 2.6.2
12:30:04 AM: Using PHP version 5.6
12:30:04 AM: Started restoring cached node modules
12:30:04 AM: Finished restoring cached node modules
12:30:04 AM: Started restoring cached go cache
12:30:05 AM: Finished restoring cached go cache
12:30:05 AM: Installing Go version 1.12
12:30:05 AM: unset GOOS;
12:30:05 AM: unset GOARCH;
12:30:05 AM: export GOROOT=‘/opt/buildhome/.gimme_cache/versions/go1.12.linux.amd64’;
12:30:05 AM: export PATH=“/opt/buildhome/.gimme_cache/versions/go1.12.linux.amd64/bin:${PATH}”;
12:30:05 AM: go version >&2;
12:30:05 AM: export GIMME_ENV=‘/opt/buildhome/.gimme_cache/env/go1.12.linux.amd64.env’;
12:30:05 AM: go version go1.12 linux/amd64
12:30:05 AM: Installing missing commands
12:30:05 AM: Verify run directory
12:30:07 AM: ​
12:30:07 AM: ────────────────────────────────────────────────────────────────
12:30:07 AM: Netlify Build
12:30:07 AM: ────────────────────────────────────────────────────────────────
12:30:07 AM: ​
12:30:07 AM: ❯ Version
12:30:07 AM: @netlify/build 26.5.0
12:30:07 AM: ​
12:30:07 AM: ❯ Flags
12:30:07 AM: baseRelDir: false
12:30:07 AM: buildId: 6233c461928ba90008ea334d
12:30:07 AM: deployId: 6233c461928ba90008ea334f
12:30:07 AM: ​
12:30:07 AM: ❯ Current directory
12:30:07 AM: /opt/build/repo
12:30:07 AM: ​
12:30:07 AM: ❯ Config file
12:30:07 AM: No config file was defined: using default values.
12:30:07 AM: ​
12:30:07 AM: ❯ Context
12:30:07 AM: production
12:30:07 AM: ​
12:30:07 AM: ────────────────────────────────────────────────────────────────
12:30:07 AM: 1. Build command from Netlify app
12:30:07 AM: ────────────────────────────────────────────────────────────────
12:30:07 AM: ​
12:30:07 AM: $ npm remove graphql && npm install gatsby && gatsby build
12:30:14 AM: npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
12:30:21 AM: npm notice created a lockfile as package-lock.json. You should commit this file.
12:30:21 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
12:30:21 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
12:30:21 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/gatsby-recipes/node_modules/chokidar/node_modules/fsevents):
12:30:21 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
12:30:21 AM: npm WARN @graphql-tools/schema@7.1.5 requires a peer of graphql@^14.0.0 || ^15.0.0 but none is installed. You must install peer dependencies yourself.
12:30:21 AM: npm WARN @graphql-tools/utils@7.10.0 requires a peer of graphql@^14.0.0 || ^15.0.0 but none is installed. You must install peer dependencies yourself.
12:30:21 AM: npm WARN @material-ui/core@1.5.1 requires a peer of react@^16.3.0 but none is installed. You must install peer dependencies yourself.
12:30:21 AM: npm WARN @material-ui/core@1.5.1 requires a peer of react-dom@^16.3.0 but none is installed. You must install peer dependencies yourself.
12:30:21 AM: npm WARN @material-ui/icons@1.1.1 requires a peer of react@^16.3.0 but none is installed. You must install peer dependencies yourself.
12:30:21 AM: npm WARN @material-ui/icons@1.1.1 requires a peer of react-dom@^16.3.0 but none is installed. You must install peer dependencies yourself.
12:30:21 AM: npm WARN @turist/fetch@7.2.0 requires a peer of node-fetch@2 but none is installed. You must install peer dependencies yourself.
12:30:21 AM: npm WARN acorn-jsx@5.3.2 requires a peer of acorn@^6.0.0 || ^7.0.0 || ^8.0.0 but none is installed. You must install peer dependencies yourself.
12:30:21 AM: npm WARN eslint-plugin-graphql@2.1.1 requires a peer of graphql@^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
12:30:21 AM: npm WARN friendly-errors-webpack-plugin@1.7.0 requires a peer of webpack@^2.0.0 || ^3.0.0 || ^4.0.0 but none is installed. You must install peer dependencies yourself.
12:30:21 AM: npm WARN graphql-compose@6.3.8 requires a peer of graphql@>=0.13.0 || >=14.0.0 || >=14.1.0 but none is installed. You must install peer dependencies yourself.
12:30:21 AM: npm WARN react-event-listener@0.6.6 requires a peer of react@^16.3.0 but none is installed. You must install peer dependencies yourself.
12:30:21 AM: npm WARN react-instantsearch-native@5.7.0 requires a peer of react-native@>= 0.32.0 but none is installed. You must install peer dependencies yourself.
12:30:22 AM: audited 3044 packages in 14.229s
12:30:24 AM: 230 packages are looking for funding
12:30:24 AM: run npm fund for details
12:30:24 AM: found 138 vulnerabilities (21 low, 62 moderate, 46 high, 9 critical)
12:30:24 AM: run npm audit fix to fix them, or npm audit for details
12:30:32 AM: npm WARN deprecated babel-preset-es2015@6.24.1: :raised_hands: Thanks for using Babel: we recommend using babel-preset-env now: please read babel-preset-es2015 -> babel-preset-env · Babel to update!
12:30:32 AM: npm WARN deprecated core-js@2.6.12: core-js@<3.4 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. Please, upgrade your dependencies to the actual version of core-js.
12:30:33 AM: npm WARN deprecated joi@12.0.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
12:30:33 AM: npm WARN deprecated postcss-cssnext@2.11.0: ‘postcss-cssnext’ has been deprecated in favor of ‘postcss-preset-env’. Read more at Deprecating cssnext
12:30:42 AM: npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
12:30:43 AM: npm WARN deprecated flatten@1.0.3: flatten is deprecated in favor of utility frameworks such as lodash.
12:30:45 AM: npm WARN deprecated extract-text-webpack-plugin@1.0.1: Deprecated. Please use GitHub - webpack-contrib/mini-css-extract-plugin: Lightweight CSS extraction plugin
12:30:48 AM: npm WARN deprecated topo@2.0.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
12:30:48 AM: npm WARN deprecated hoek@4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
12:30:50 AM: npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
12:30:53 AM: npm WARN deprecated pkg-resolve@0.1.14: Not maintained anymore.
12:30:54 AM: npm WARN deprecated sane@1.7.0: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
12:31:04 AM: npm WARN deprecated redux-devtools-core@0.2.1: Package moved to @redux-devtools/app.
12:31:04 AM: npm WARN deprecated redux-devtools-instrument@1.10.0: Package moved to @redux-devtools/instrument.
12:31:05 AM: npm WARN deprecated remotedev-serialize@0.1.9: Package moved to @redux-devtools/serialize.
12:31:05 AM: npm WARN deprecated uuid@3.2.1: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See There’s Math.random(), and then there’s Math.random() · V8 for details.
12:31:07 AM: npm WARN deprecated debug@4.1.1: 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. (ReDos Vulnerability Regression Visibility Notice · Issue #797 · debug-js/debug · GitHub)
12:31:11 AM: npm WARN deprecated joi@9.0.0-0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
12:31:11 AM: npm WARN deprecated items@2.1.2: This module has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version of hapi to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
12:31:20 AM: npm WARN @graphql-tools/schema@7.1.5 requires a peer of graphql@^14.0.0 || ^15.0.0 but none is installed. You must install peer dependencies yourself.
12:31:20 AM: npm WARN @graphql-tools/utils@7.10.0 requires a peer of graphql@^14.0.0 || ^15.0.0 but none is installed. You must install peer dependencies yourself.
12:31:20 AM: npm WARN @material-ui/core@1.5.1 requires a peer of react@^16.3.0 but none is installed. You must install peer dependencies yourself.
12:31:20 AM: npm WARN @material-ui/core@1.5.1 requires a peer of react-dom@^16.3.0 but none is installed. You must install peer dependencies yourself.
12:31:20 AM: npm WARN @material-ui/icons@1.1.1 requires a peer of react@^16.3.0 but none is installed. You must install peer dependencies yourself.
12:31:20 AM: npm WARN @material-ui/icons@1.1.1 requires a peer of react-dom@^16.3.0 but none is installed. You must install peer dependencies yourself.
12:31:20 AM: npm WARN @turist/fetch@7.2.0 requires a peer of node-fetch@2 but none is installed. You must install peer dependencies yourself.
12:31:20 AM: npm WARN acorn-jsx@5.3.2 requires a peer of acorn@^6.0.0 || ^7.0.0 || ^8.0.0 but none is installed. You must install peer dependencies yourself.
12:31:20 AM: npm WARN eslint-plugin-graphql@2.1.1 requires a peer of graphql@^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
12:31:20 AM: npm WARN graphql-compose@6.3.8 requires a peer of graphql@>=0.13.0 || >=14.0.0 || >=14.1.0 but none is installed. You must install peer dependencies yourself.
12:31:20 AM: npm WARN react-event-listener@0.6.6 requires a peer of react@^16.3.0 but none is installed. You must install peer dependencies yourself.
12:31:20 AM: npm WARN react-instantsearch-native@5.7.0 requires a peer of react-native@>= 0.32.0 but none is installed. You must install peer dependencies yourself.
12:31:20 AM: npm WARN friendly-errors-webpack-plugin@1.7.0 requires a peer of webpack@^2.0.0 || ^3.0.0 || ^4.0.0 but none is installed. You must install peer dependencies yourself.
12:31:20 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/fsevents):
12:31:20 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
12:31:20 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/gatsby-recipes/node_modules/fsevents):
12:31:20 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
12:31:20 AM: + gatsby@1.9.279
12:31:20 AM: updated 1 package and audited 3044 packages in 56.137s
12:31:22 AM: 228 packages are looking for funding
12:31:22 AM: run npm fund for details
12:31:22 AM: found 138 vulnerabilities (21 low, 62 moderate, 46 high, 9 critical)
12:31:22 AM: run npm audit fix to fix them, or npm audit for details
12:31:24 AM: success delete html and css files from previous builds — 0.008 s
12:31:24 AM: success open and validate gatsby-config — 0.006 s
12:31:24 AM: success copy gatsby files — 0.013 s
12:31:25 AM: success onPreBootstrap — 0.826 s
12:31:25 AM: success source and transform nodes — 0.665 s
12:31:26 AM: success building schema — 0.313 s
12:31:26 AM: success createLayouts — 0.010 s
12:31:26 AM: success createPages — 0.174 s
12:31:26 AM: success createPagesStatefully — 0.009 s
12:31:26 AM: success onPreExtractQueries — 0.003 s
12:31:26 AM: success update schema — 0.128 s
12:31:26 AM: success extract queries from components — 0.148 s
12:31:32 AM: success run graphql queries — 6.292 s
12:31:32 AM: success write out page data — 0.035 s
12:31:32 AM: success write out redirect data — 0.001 s
12:31:47 AM:
12:31:47 AM: info bootstrap finished - 24.968 s
12:31:47 AM:
12:31:47 AM: success onPostBootstrap — 0.001 s
12:31:54 AM: success Building CSS — 6.615 s
12:32:16 AM: success Building production JavaScript bundles — 22.034 s
12:32:24 AM: success Building static HTML for pages — 8.519 s
12:32:26 AM: Total precache size is about 618 kB for 5 resources.
12:32:26 AM: info Done building in 63.931 sec
12:32:26 AM: ​
12:32:26 AM: (build.command completed in 2m 19.3s)
12:32:26 AM: ​
12:32:26 AM: ────────────────────────────────────────────────────────────────
12:32:26 AM: 2. Deploy site
12:32:26 AM: ────────────────────────────────────────────────────────────────
12:32:26 AM: ​
12:32:27 AM: Creating deploy upload records
12:32:26 AM: Starting to deploy site from ‘public’
12:32:26 AM: Creating deploy tree asynchronously
12:32:29 AM: 104 new files to upload
12:32:29 AM: 0 new functions to upload
12:32:35 AM: Site deploy was successfully initiated
12:32:35 AM: ​
12:32:35 AM: (Deploy site completed in 8.3s)
12:32:35 AM: ​
12:32:35 AM: ────────────────────────────────────────────────────────────────
12:32:35 AM: Netlify Build Complete
12:32:35 AM: ────────────────────────────────────────────────────────────────
12:32:35 AM: ​
12:32:35 AM: (Netlify Build completed in 2m 27.7s)
12:32:35 AM: Caching artifacts
12:32:35 AM: Started saving node modules
12:32:35 AM: Finished saving node modules
12:32:35 AM: Started saving build plugins
12:32:35 AM: Finished saving build plugins
12:32:35 AM: Started saving pip cache
12:32:35 AM: Finished saving pip cache
12:32:35 AM: Started saving emacs cask dependencies
12:32:35 AM: Finished saving emacs cask dependencies
12:32:35 AM: Started saving maven dependencies
12:32:35 AM: Finished saving maven dependencies
12:32:35 AM: Started saving boot dependencies
12:32:35 AM: Finished saving boot dependencies
12:32:35 AM: Started saving rust rustup cache
12:32:35 AM: Finished saving rust rustup cache
12:32:36 AM: Starting post processing
12:32:35 AM: Started saving go dependencies
12:32:36 AM: Post processing - HTML
12:32:36 AM: Finished saving go dependencies
12:32:36 AM: Build script success
12:32:51 AM: Processing form - contact
12:32:51 AM: Detected form fields:
12:32:51 AM: - name
12:32:51 AM: - email
12:32:51 AM: - message
12:32:52 AM: - bot-field
12:32:52 AM: Post processing - header rules
12:32:52 AM: Post processing - redirect rules
12:32:53 AM: Post processing done
12:32:56 AM: Site is live :sparkles:
12:33:32 AM: Finished processing build request in 3m52.921567209s

14

Hey @rccclr,

More than the updated build image version, you need to be concerned about using outdated libraries in your project. You’re missing out on lot of security updates, speed improvements and feature updates. Node 10 has stopped receiving support, and we can’t continue to debug it as well. If one of our updates have broken Node 10, unfortunately, that’s not something that can be fixed.

You’re using ancient versions of the packages which includes Gatsby 1. We recommend you to upgrade the project to at least Node 14 (or Node 16 with future in mind), and Gatsby 4 so we can debug this further.

15

We have this same issue. Builds were fine until March. We have an old version of gatsby and an old version of node. Upgrading from v1 of Gatsby doesn’t seem like a quick fix. There has to be a solution other than “upgrade all your libs”.

16

There could be, but unfortunately, we cannot be debugging an issue that tools used in which are not supported by their own creators.

Gatsby doesn’t provide support for anything less than Gatsby 3 at the moment, as far as I’m aware.
Node 10 has been declared out of support too.