Gatsby-runner build failed

Hi, I know it’s experimental but I just wanted to try. I followed all the instruction here:

1.installed npm install @netlify/gatsby-runner
2. add netlify toml file with the plugin
3. change the build command to “build” : “gatsby-runner”

Then I tried a local npm run build and it seems to work as expected. See end of the log below:

  ╭────────────────────────────────────────────────────────────────╮
  │                                                                │
  │   (SSG) Generated at build time                                │
  │ D (DSG) Deferred static generation - page generated at runtime │
  │ ∞ (SSR) Server-side renders at runtime (uses getServerData)    │
  │ λ (Function) Gatsby function                                   │
  │                                                                │
  ╰────────────────────────────────────────────────────────────────╯

Deferred processing 1640 images until runtime. Moved 534 originals
Built site using the experimental Netlify Gatsby build runner. 
Please report any issues: https://ntl.fyi/gatsby-runner

But when I pushed everything to netlify I got some errors. Here is the log:

1:52:55 PM: Build ready to start
1:52:56 PM: build-image version: ac716c5be7f79fe384a0f3759e8ef612cb821a37 (xenial)
1:52:56 PM: build-image tag: v3.13.0
1:52:56 PM: buildbot version: 515e5c33287d8b909c004fcf2e460e8645e8c1c6
1:52:56 PM: Fetching cached dependencies
1:52:56 PM: Failed to fetch cache, continuing with build
1:52:56 PM: Starting to prepare the repo for build
1:52:57 PM: No cached dependencies found. Cloning fresh repo
1:52:57 PM: git clone https://github.com/AnnieTaylorCHEN/petiteandminimalblog
1:53:00 PM: Preparing Git Reference refs/heads/master
1:53:02 PM: Parsing package.json dependencies
1:53:03 PM: Starting build script
1:53:03 PM: Installing dependencies
1:53:03 PM: Python version set to 2.7
1:53:04 PM: Downloading and installing node v14.19.3...
1:53:04 PM: Downloading https://nodejs.org/dist/v14.19.3/node-v14.19.3-linux-x64.tar.xz...
1:53:04 PM: Computing checksum with sha256sum
1:53:05 PM: Checksums matched!
1:53:07 PM: Now using node v14.19.3 (npm v6.14.17)
1:53:07 PM: Started restoring cached build plugins
1:53:07 PM: Finished restoring cached build plugins
1:53:08 PM: Attempting ruby version 2.6.2, read from environment
1:53:09 PM: Using ruby version 2.6.2
1:53:09 PM: Using PHP version 5.6
1:53:09 PM: No npm workspaces detected
1:53:09 PM: Started restoring cached node modules
1:53:09 PM: Finished restoring cached node modules
1:53:10 PM: Installing NPM modules using NPM version 6.14.17
2:06:19 PM: npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
2:06:19 PM: > @parcel/watcher@2.0.5 install /opt/build/repo/node_modules/@parcel/watcher
2:06:19 PM: > node-gyp-build
2:06:19 PM: > msgpackr-extract@1.1.4 install /opt/build/repo/node_modules/msgpackr-extract
2:06:19 PM: > node-gyp-build-optional-packages
2:06:20 PM: > lmdb@2.3.10 install /opt/build/repo/node_modules/@parcel/cache/node_modules/lmdb
2:06:20 PM: > node-gyp-build-optional-packages
2:06:20 PM: > lmdb@2.5.2 install /opt/build/repo/node_modules/lmdb
2:06:20 PM: > node-gyp-build-optional-packages
2:06:20 PM: > sharp@0.30.7 install /opt/build/repo/node_modules/sharp
2:06:20 PM: > (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)
2:06:22 PM: sharp: Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.12.2/libvips-8.12.2-linux-x64.tar.br
2:06:22 PM: sharp: Integrity check passed for linux-x64
2:06:23 PM: > core-js@2.6.12 postinstall /opt/build/repo/node_modules/babel-runtime/node_modules/core-js
2:06:23 PM: > node -e "try{require('./postinstall')}catch(e){}"
2:06:23 PM: > core-js@3.23.3 postinstall /opt/build/repo/node_modules/core-js
2:06:23 PM: > node -e "try{require('./postinstall')}catch(e){}"
2:06:23 PM: > core-js-pure@3.19.1 postinstall /opt/build/repo/node_modules/core-js-pure
2:06:23 PM: > node -e "try{require('./postinstall')}catch(e){}"
2:06:24 PM: > gatsby-telemetry@3.17.0 postinstall /opt/build/repo/node_modules/gatsby-telemetry
2:06:24 PM: > node src/postinstall.js || true
2:06:24 PM: > gatsby-cli@4.17.1 postinstall /opt/build/repo/node_modules/gatsby-cli
2:06:24 PM: > node scripts/postinstall.js
2:06:24 PM: > gatsby@4.17.2 postinstall /opt/build/repo/node_modules/gatsby
2:06:24 PM: > node scripts/postinstall.js
2:06:24 PM: > annies-gatsby-starter-default@0.1.0 prepare /opt/build/repo
2:06:24 PM: > husky install
2:06:24 PM: husky - Git hooks installed
2:06:26 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: msgpackr-extract-win32-x64@1.1.0 (node_modules/msgpackr-extract-win32-x64):
2:06:26 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for msgpackr-extract-win32-x64@1.1.0: wanted {"os":"win32","arch":"x64"} (current: {"os":"linux","arch":"x64"})
2:06:26 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: msgpackr-extract-linux-arm64@1.1.0 (node_modules/msgpackr-extract-linux-arm64):
2:06:26 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for msgpackr-extract-linux-arm64@1.1.0: wanted {"os":"linux","arch":"arm64"} (current: {"os":"linux","arch":"x64"})
2:06:26 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: msgpackr-extract-linux-arm@1.1.0 (node_modules/msgpackr-extract-linux-arm):
2:06:26 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for msgpackr-extract-linux-arm@1.1.0: wanted {"os":"linux","arch":"arm"} (current: {"os":"linux","arch":"x64"})
2:06:26 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: msgpackr-extract-darwin-x64@1.1.0 (node_modules/msgpackr-extract-darwin-x64):
2:06:26 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for msgpackr-extract-darwin-x64@1.1.0: wanted {"os":"darwin","arch":"x64"} (current: {"os":"linux","arch":"x64"})
2:06:26 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: msgpackr-extract-darwin-arm64@1.1.0 (node_modules/msgpackr-extract-darwin-arm64):
2:06:26 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for msgpackr-extract-darwin-arm64@1.1.0: wanted {"os":"darwin","arch":"arm64"} (current: {"os":"linux","arch":"x64"})
2:06:26 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: lmdb-win32-x64@2.3.10 (node_modules/lmdb-win32-x64):
2:06:26 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for lmdb-win32-x64@2.3.10: wanted {"os":"win32","arch":"x64"} (current: {"os":"linux","arch":"x64"})
2:06:26 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: lmdb-linux-arm64@2.3.10 (node_modules/lmdb-linux-arm64):
2:06:26 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for lmdb-linux-arm64@2.3.10: wanted {"os":"linux","arch":"arm64"} (current: {"os":"linux","arch":"x64"})
2:06:26 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: lmdb-linux-arm@2.3.10 (node_modules/lmdb-linux-arm):
2:06:26 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for lmdb-linux-arm@2.3.10: wanted {"os":"linux","arch":"arm"} (current: {"os":"linux","arch":"x64"})
2:06:26 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: lmdb-darwin-x64@2.3.10 (node_modules/lmdb-darwin-x64):
2:06:26 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for lmdb-darwin-x64@2.3.10: wanted {"os":"darwin","arch":"x64"} (current: {"os":"linux","arch":"x64"})
2:06:26 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: lmdb-darwin-arm64@2.3.10 (node_modules/lmdb-darwin-arm64):
2:06:26 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for lmdb-darwin-arm64@2.3.10: wanted {"os":"darwin","arch":"arm64"} (current: {"os":"linux","arch":"x64"})
2:06:26 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
2:06:26 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2:06:26 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @lmdb/lmdb-win32-x64@2.5.2 (node_modules/@lmdb/lmdb-win32-x64):
2:06:26 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @lmdb/lmdb-win32-x64@2.5.2: wanted {"os":"win32","arch":"x64"} (current: {"os":"linux","arch":"x64"})
2:06:26 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @lmdb/lmdb-linux-arm64@2.5.2 (node_modules/@lmdb/lmdb-linux-arm64):
2:06:26 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @lmdb/lmdb-linux-arm64@2.5.2: wanted {"os":"linux","arch":"arm64"} (current: {"os":"linux","arch":"x64"})
2:06:26 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @lmdb/lmdb-linux-arm@2.5.2 (node_modules/@lmdb/lmdb-linux-arm):
2:06:26 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @lmdb/lmdb-linux-arm@2.5.2: wanted {"os":"linux","arch":"arm"} (current: {"os":"linux","arch":"x64"})
2:06:26 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @lmdb/lmdb-darwin-x64@2.5.2 (node_modules/@lmdb/lmdb-darwin-x64):
2:06:26 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @lmdb/lmdb-darwin-x64@2.5.2: wanted {"os":"darwin","arch":"x64"} (current: {"os":"linux","arch":"x64"})
2:06:26 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @lmdb/lmdb-darwin-arm64@2.5.2 (node_modules/@lmdb/lmdb-darwin-arm64):
2:06:26 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @lmdb/lmdb-darwin-arm64@2.5.2: wanted {"os":"darwin","arch":"arm64"} (current: {"os":"linux","arch":"x64"})
2:06:26 PM: added 1945 packages from 1218 contributors and audited 1964 packages in 795.955s
2:06:27 PM: 320 packages are looking for funding
2:06:27 PM:   run `npm fund` for details
2:06:28 PM: found 16 vulnerabilities (9 moderate, 7 high)
2:06:28 PM:   run `npm audit fix` to fix them, or `npm audit` for details
2:06:28 PM: NPM modules installed
2:06:28 PM: Started restoring cached go cache
2:06:28 PM: Finished restoring cached go cache
2:06:28 PM: Installing Go version 1.12
2:06:33 PM: unset GOOS;
2:06:33 PM: unset GOARCH;
2:06:33 PM: export GOROOT='/opt/buildhome/.gimme_cache/versions/go1.12.linux.amd64';
2:06:33 PM: export PATH="/opt/buildhome/.gimme_cache/versions/go1.12.linux.amd64/bin:${PATH}";
2:06:33 PM: go version >&2;
2:06:33 PM: export GIMME_ENV="/opt/buildhome/.gimme_cache/env/go1.12.linux.amd64.env"
2:06:33 PM: go version go1.12 linux/amd64
2:06:33 PM: Installing missing commands
2:06:33 PM: Verify run directory
2:06:34 PM: ​
2:06:34 PM: ────────────────────────────────────────────────────────────────
2:06:34 PM:   Netlify Build                                                 
2:06:34 PM: ────────────────────────────────────────────────────────────────
2:06:34 PM: ​
2:06:34 PM: ❯ Version
2:06:34 PM:   @netlify/build 27.3.0
2:06:34 PM: ​
2:06:34 PM: ❯ Flags
2:06:34 PM:   baseRelDir: true
2:06:34 PM:   buildId: 62bee016fbdd2f53cb3af14a
2:06:34 PM:   deployId: 62bee016fbdd2f53cb3af14c
2:06:34 PM: ​
2:06:34 PM: ❯ Current directory
2:06:34 PM:   /opt/build/repo
2:06:34 PM: ​
2:06:34 PM: ❯ Config file
2:06:34 PM:   /opt/build/repo/netlify.toml
2:06:34 PM: ​
2:06:34 PM: ❯ Context
2:06:34 PM:   production
2:06:35 PM: ​
2:06:35 PM: ❯ Installing plugins
2:06:35 PM:    - netlify-plugin-no-more-404@0.0.15
2:06:35 PM:    - @netlify/plugin-gatsby@3.2.4
2:06:51 PM: ​
2:06:51 PM: ❯ Loading plugins
2:06:51 PM:    - netlify-plugin-no-more-404@0.0.15 from Netlify app
2:06:51 PM:    - @netlify/plugin-gatsby@3.2.4 from Netlify app
2:06:51 PM:    - @netlify/gatsby-runner@1.1.10 from netlify.toml and package.json
2:06:54 PM: ​
2:06:54 PM: ────────────────────────────────────────────────────────────────
2:06:54 PM:   1. @netlify/plugin-gatsby (onPreBuild event)                  
2:06:54 PM: ────────────────────────────────────────────────────────────────
2:06:54 PM: ​
2:06:54 PM: No Gatsby cache found. Building fresh.
2:06:54 PM: ​
2:06:54 PM: (@netlify/plugin-gatsby onPreBuild completed in 138ms)
2:06:54 PM: ​
2:06:54 PM: ────────────────────────────────────────────────────────────────
2:06:54 PM:   2. Build command from Netlify app                             
2:06:54 PM: ────────────────────────────────────────────────────────────────
2:06:54 PM: ​
2:06:54 PM: $ npm run build
2:06:55 PM: > annies-gatsby-starter-default@0.1.0 build /opt/build/repo
2:06:55 PM: > gatsby-runner
2:06:55 PM: Building site with the Netlify Gatsby build runner.
2:06:59 PM: not finished compile gatsby files - 1.505s
2:06:59 PM: Gatsby exited with code 1
2:06:59 PM: npm ERR! code ELIFECYCLE
2:06:59 PM: npm ERR! errno 1
2:06:59 PM: npm ERR! annies-gatsby-starter-default@0.1.0 build: `gatsby-runner`
2:06:59 PM: npm ERR! Exit status 1
2:06:59 PM: npm ERR!
2:06:59 PM: npm ERR! Failed at the annies-gatsby-starter-default@0.1.0 build script.
2:06:59 PM: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2:06:59 PM: npm ERR! A complete log of this run can be found in:
2:06:59 PM: npm ERR!     /opt/buildhome/.npm/_logs/2022-07-01T12_06_59_928Z-debug.log
2:07:00 PM: ​
2:07:00 PM: ────────────────────────────────────────────────────────────────
2:07:00 PM:   "build.command" failed                                        
2:07:00 PM: ────────────────────────────────────────────────────────────────
2:07:00 PM: ​
2:07:00 PM:   Error message
2:07:00 PM:   Command failed with exit code 1: npm run build (https://ntl.fyi/exit-code-1)
2:07:00 PM: ​
2:07:00 PM:   Error location
2:07:00 PM:   In Build command from Netlify app:
2:07:00 PM:   npm run build
2:07:00 PM: ​
2:07:00 PM:   Resolved config
2:07:00 PM:   build:
2:07:00 PM:     command: npm run build
2:07:00 PM:     commandOrigin: ui
2:07:00 PM:     environment:
2:07:00 PM:       - ALGOLIA_ADMIN_KEY
2:07:00 PM:       - GATSBY_ALGOLIA_APP_ID
2:07:00 PM:       - GATSBY_ALGOLIA_SEARCH_KEY
2:07:00 PM:       - NODE_VERSION
2:07:00 PM:     publish: /opt/build/repo/public
2:07:00 PM:     publishOrigin: ui
2:07:00 PM:   plugins:
2:07:00 PM:     - inputs: {}
2:07:00 PM:       origin: ui
2:07:00 PM:       package: netlify-plugin-no-more-404
2:07:00 PM:     - inputs: {}
2:07:00 PM:       origin: ui
2:07:00 PM:       package: '@netlify/plugin-gatsby'
2:07:00 PM:     - inputs: {}
2:07:00 PM:       origin: config
2:07:00 PM:       package: '@netlify/gatsby-runner'
2:07:00 PM: Caching artifacts
2:07:00 PM: Started saving node modules
2:07:00 PM: Finished saving node modules
2:07:00 PM: Started saving build plugins
2:07:00 PM: Finished saving build plugins
2:07:00 PM: Started saving pip cache
2:07:00 PM: Finished saving pip cache
2:07:00 PM: Started saving emacs cask dependencies
2:07:00 PM: Finished saving emacs cask dependencies
2:07:00 PM: Started saving maven dependencies
2:07:00 PM: Finished saving maven dependencies
2:07:00 PM: Started saving boot dependencies
2:07:00 PM: Finished saving boot dependencies
2:07:00 PM: Started saving rust rustup cache
2:07:00 PM: Finished saving rust rustup cache
2:07:00 PM: Started saving go dependencies
2:07:01 PM: Finished saving go dependencies
2:07:03 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
2:07:03 PM: Creating deploy upload records
2:07:03 PM: Failing build: Failed to build site
2:07:03 PM: Failed during stage 'building site': Build script returned non-zero exit code: 2 (https://ntl.fyi/exit-code-2)
2:07:03 PM: Finished processing build request in 14m7.391758322s

What caused this error and how do I fix it? Thanks!

hmm, i’m not entirely convinced this is a problem with the runner, but i think it may be a build command issue. could you paste the contents of your package.json here please? and a screenshot of your build & deploy settings for that repo?

Here is the package json:

{
  "name": "annies-gatsby-starter-default",
  "private": true,
  "description": "NA",
  "version": "0.1.0",
  "author": "Annie",
  "dependencies": {
    "@netlify/gatsby-runner": "^1.1.10",
    "algoliasearch": "^4.9.0",
    "disqus-react": "^1.0.8",
    "dotenv": "^8.2.0",
    "gatsby": "^4.0.0",
    "gatsby-image": "^2.3.5",
    "gatsby-plugin-algolia": "^0.26.0",
    "gatsby-plugin-google-gtag": "^4.1.0-next.0",
    "gatsby-plugin-html-attributes": "^1.0.5",
    "gatsby-plugin-image": "^2.1.0-next.0",
    "gatsby-plugin-manifest": "^4.1.0-next.0",
    "gatsby-plugin-netlify": "^5.0.0",
    "gatsby-plugin-offline": "^5.1.0-next.0",
    "gatsby-plugin-react-helmet": "^5.1.0-next.0",
    "gatsby-plugin-robots-txt": "^1.7.1",
    "gatsby-plugin-sharp": "^4.1.0-next.0",
    "gatsby-plugin-sitemap": "^5.1.0-next.0",
    "gatsby-plugin-styled-components": "^5.1.0-next.0",
    "gatsby-remark-images": "^6.1.0-next.0",
    "gatsby-source-filesystem": "^4.1.0-next.0",
    "gatsby-transformer-remark": "^5.1.0-next.0",
    "gatsby-transformer-sharp": "^4.1.0-next.0",
    "postcss": "^8.2.10",
    "postcss-loader": "^5.2.0",
    "prop-types": "^15.7.2",
    "react": "^16.13.1",
    "react-dom": "^16.13.1",
    "react-helmet": "^5.2.1",
    "react-instantsearch-dom": "^6.10.3",
    "react-share": "^4.4.0",
    "styled-components": "^5.2.3",
    "styled-icons": "^9.5.0"
  },
  "devDependencies": {
    "husky": "^7.0.4",
    "prettier": "^1.19.1"
  },
  "keywords": [
    "gatsby"
  ],
  "license": "MIT",
  "scripts": {
    "build": "gatsby-runner",
    "develop": "gatsby develop",
    "format": "prettier --write \"**/*.{js,jsx,json,md}\"",
    "start": "npm run develop",
    "serve": "gatsby serve",
    "clean": "gatsby clean",
    "info": "gatsby info --clipboard",
    "test": "echo \"Write tests! -> https://gatsby.dev/unit-testing\" && exit 1",
    "prepare": "husky install"
  },
  "lint-staged": {
    "*.js|jsx|ts|tsx": [
      "prettier --write"
    ]
  },
  "repository": {
    "type": "git",
    "url": "https://github.com/gatsbyjs/gatsby-starter-default"
  },
  "bugs": {
    "url": "https://github.com/gatsbyjs/gatsby/issues"
  }
}

screenshots of build and deploy setting:

Hi @AnnieTC,

We would try to discuss this with the developers this week and let you know the findings.

In the meanwhile, my hunch is that, your build could be running out of memory. From our logs, I can see that it took up to 3 GB of RAM and that’s the minimum that we guarantee. You can sometimes get up to 6 GB, but that’s subject to availability.

More on that here:

Ok, that’ll be great. Yeah I haven’t updated for a while so it seems there is no cache. I have a lot of images so that’s why I am curious to try this new thing.

Hey @AnnieTC,

Is it possible for you to share your repo by any chance? Our devs were trying to look at it but there doesn’t appear to be any obvious first-look problem here.

Hi, it’s a private repo but if you provide one or two developer’s github name I could invite them as collaborator temporarily to troubleshoot the issue. Thanks!

Hey @AnnieTC,

Feel free to share it with: ascorbic (Matt Kane) · GitHub for this one

Great I’ve invited Matt. I’ll be happy to hear what happened and how we could solve this issue.

Hello there, any updates on this?

Hey there, @AnnieTC

Thanks for following up. We have reached out to the engineer working on this issue and will let you know when we have more updates.

Today I tried again and it didn’t work and I changed it back to “gatsby build” and my local run was successful, however, it didn’t run well on Netlify. This old command used to work though. Here is the error message

────────────────────────────────────────────────────────────────
5:42:48 PM:   2. Build command from Netlify app                             
5:42:48 PM: ────────────────────────────────────────────────────────────────
5:42:48 PM: ​
5:42:48 PM: $ npm run build
5:42:48 PM: > annies-gatsby-starter-default@0.1.0 build /opt/build/repo
5:42:48 PM: > gatsby build
5:42:52 PM: error Failed to compile Gatsby files (Error):
5:42:52 PM: Could not resolve module "@parcel/namer-default" from "/opt/build/repo/node\_modules/@gatsbyjs/parcel-namer-relative-to-cwd/lib/index.js".
5:42:52 PM: not finished compile gatsby files - 1.429s
5:42:52 PM: npm ERR! code ELIFECYCLE
5:42:52 PM: npm ERR! errno 1
5:42:52 PM: npm ERR! annies-gatsby-starter-default@0.1.0 build: `gatsby build`
5:42:52 PM: npm ERR! Exit status 1
5:42:52 PM: npm ERR!
5:42:52 PM: npm ERR! Failed at the annies-gatsby-starter-default@0.1.0 build script.
5:42:52 PM: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
5:42:52 PM: npm ERR! A complete log of this run can be found in:
5:42:52 PM: npm ERR!     /opt/buildhome/.npm/_logs/2022-07-21T15_42_52_818Z-debug.log
5:42:52 PM: ​
5:42:52 PM: ────────────────────────────────────────────────────────────────
5:42:52 PM:   "build.command" failed                                        
5:42:52 PM: ────────────────────────────────────────────────────────────────
5:42:52 PM: ​
5:42:52 PM:   Error message
5:42:52 PM:   Command failed with exit code 1: npm run build (https://ntl.fyi/exit-code-1)
5:42:52 PM: ​
5:42:52 PM:   Error location
5:42:52 PM:   In Build command from Netlify app:
5:42:52 PM:   npm run build

Any idea why?

Ok, me again. I referred to this link:

and managed to solve my above issue with gatsby build.

The “gatsby-runner” issue remains to be answered. :slight_smile:

Hi there, it’s been almost a month. Any updates on this?

Hey there, @AnnieTC :wave:

My apologies for the delay. I have followed up on our open internal issue and will report back when we have more information. Thanks for your patience!

Hey @AnnieTC,

The team tried to understand the root cause of this issue and we’re still not 100% sure, but it looks like there’s a symlink loop in your Node Modules folder. This is why Gatsby is failing to load the config files. Are you aware of any loops or something that you might have created yourself?

Hi there… hmm, I can’t think of anything I’ve done to create this. Matt should still have access to the repo, maybe he can take a look? It’s really a simple blog style website of generated posts plus pages. Currently I am using the old gatsby build and things seem to be working.

Hi again Annie and very sorry to be slow to get back to you! I just got a chance to meet with our dev team on this and they are pretty much out of direct actionable ideas, so let’s talk about what can be done to work around this, or to give us a path to something more directly actionable for us to help with.

First off, it is possible you don’t even need the gatsby-runner package, which is an experimental piece of software (as mentioned in its README here: GitHub - netlify/gatsby-runner: This is an experimental build runner for Gatsby on Netlify, to improve build times for sites with lots of images. . Have you tried without it? Generally you should only need it for very image heavy sites where you need to process images at build time, which may not be a need you even have.

If you feel sure you need it for today’s workflow, no problem. But you will have to make a decision as to how you want to proceed:

  • This is beyond what our Support team could help with, so for our dev team to even consider doing any more work here, we’d need you to create a public repo showing the problem, hopefully with a minimal site (so, create a template site, add one image, and make the repo public and link it here). I can’t promise our dev team can look into it if you do since this is not an officially supported package, but I can promise we won’t, if we don’t have such a reproduction case.
  • I’d suggest that image processing in gatsby is often fraught with peril anyway (actually, let me just show you someone else suggesting it: 5 Optimizations to Get Faster Gatsby Builds Today). Do you need to process images at build time, or is it a possibility you could do a one time processing run, save the results to git, and avoid using gatsby image handling at all? Then you definitely don’t need the gatsby-runner package :slight_smile:

Let me know what you think!

Hi fool (ah, feel awkward to call you this), yeah your suggestion makes sense. I just wanted to try things out and it’s not a urgent matter for me to have it right now. I’ve since switched back to previous build method. Let’s consider this close by now and thank you all for your help.