Gatsby site fails to build on Netlify, but works locally

site: beta-tonycre8.netlify.app (or https://www.beta.tonycre8.co.uk)

Hey guys, having a little issue here. Trying to upload my Gatsby website onto Netlify as I’ve done in the past. However, I seem to be getting build errors here that I’m not getting when I build the project locally. Let’s compare some logs to give us a boost.

This is the local build

$ gatsby build
success open and validate gatsby-configs - 0.168s
success load plugins - 19.575s
warn The Google Analytics plugin requires a tracking ID. Did you mean to add it?
success onPreInit - 0.091s
success delete html and css files from previous builds - 0.181s
success initialize cache - 0.013s
success copy gatsby files - 0.904s
warn gatsby-plugin-feed was initialized in gatsby-config.js without a feeds option.
This means that the plugin will use the internal RSS feed creation, which may not match your use case.
This behavior will be removed in the next major release of gatsby-plugin-feed.
For more info, check out: https://gatsby.dev/adding-rss-feed
success onPreBootstrap - 0.143s
success createSchemaCustomization - 2.830s
success source and transform nodes - 0.992s
success building schema - 1.109s
success createPages - 0.187s
success createPagesStatefully - 0.318s
success onPreExtractQueries - 0.003s
success update schema - 0.080s
success extract queries from components - 1.383s
success write out requires - 0.059s
success write out redirect data - 0.007s
success Build manifest and related icons - 0.289s
success onPostBootstrap - 0.432s
⠀
info bootstrap finished - 87.339 s
⠀
success Building production JavaScript and CSS bundles - 43.384s
success Rewriting compilation hashes - 0.012s
success run queries - 44.799s - 23/23 0.51/s
success Building static HTML for pages - 5.120s - 20/20 3.91/s
info Done building in 137.758 sec

This is the Netlify build

5:43:06 PM: Build ready to start
5:43:08 PM: build-image version: 2dbd444fcdce00cf06325060a8238d5ae3e86774
5:43:08 PM: build-image tag: v3.3.7
5:43:08 PM: buildbot version: d305548225ac57bb00eb5a596b0b8674e76a4681
5:43:08 PM: Fetching cached dependencies
5:43:08 PM: Starting to download cache of 191.7MB
5:43:10 PM: Finished downloading cache in 1.579883728s
5:43:10 PM: Starting to extract cache
5:43:18 PM: Finished extracting cache in 8.516565393s
5:43:18 PM: Finished fetching cache in 10.143509197s
5:43:18 PM: Starting to prepare the repo for build
5:43:19 PM: Preparing Git Reference refs/heads/master
5:43:20 PM: Starting build script
5:43:20 PM: Installing dependencies
5:43:21 PM: Started restoring cached node version
5:43:24 PM: Finished restoring cached node version
5:43:25 PM: v10.20.1 is already installed.
5:43:25 PM: Now using node v10.20.1 (npm v6.14.4)
5:43:26 PM: Attempting ruby version 2.6.2, read from environment
5:43:27 PM: Using ruby version 2.6.2
5:43:27 PM: Using PHP version 5.6
5:43:27 PM: Started restoring cached node modules
5:43:27 PM: Finished restoring cached node modules
5:43:27 PM: Installing NPM modules using NPM version 6.14.4
5:43:43 PM: npm
5:43:43 PM:  WARN bootstrap@4.4.1 requires a peer of jquery@1.9.1 - 3 but none is installed. You must install peer dependencies yourself.
5:43:43 PM: npm
5:43:43 PM:  WARN slick-carousel@1.8.1 requires a peer of jquery@>=1.8.0 but none is installed. You must install peer dependencies yourself.
5:43:43 PM: npm WARN
5:43:43 PM:  tsutils@3.17.1 requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
5:43:43 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/chokidar/node_modules/fsevents):
5:43:43 PM: npm WARN
5:43:43 PM:  notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
5:43:43 PM: npm
5:43:43 PM: WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules/fsevents):
5:43:43 PM: npm
5:43:43 PM:  WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
5:43:43 PM: added 6 packages from 45 contributors, removed 1 package and audited 30130 packages in 14.911s
5:43:45 PM: 74 packages are looking for funding
5:43:45 PM:   run `npm fund` for details
5:43:45 PM: found 86 vulnerabilities (75 low, 2 moderate, 9 high)
5:43:45 PM:   run `npm audit fix` to fix them, or `npm audit` for details
5:43:45 PM: NPM modules installed
5:43:45 PM: Started restoring cached go cache
5:43:45 PM: Finished restoring cached go cache
5:43:45 PM: unset GOOS;
5:43:45 PM: unset GOARCH;
5:43:45 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64';
5:43:45 PM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}";
5:43:45 PM: go version >&2;
5:43:45 PM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.12.linux.amd64.env';
5:43:45 PM: go version go1.12 linux/amd64
5:43:45 PM: Installing missing commands
5:43:45 PM: Verify run directory
5:43:45 PM: Executing user command: gatsby build
5:43:48 PM: success open and validate gatsby-configs - 0.072s
5:43:49 PM: success load plugins - 1.023s
5:43:49 PM: warning The Google Analytics plugin requires a tracking ID. Did you mean to add it?
5:43:49 PM: success onPreInit - 0.009s
5:43:49 PM: success delete html and css files from previous builds - 0.012s
5:43:49 PM: success initialize cache - 0.010s
5:43:49 PM: success copy gatsby files - 0.037s
5:43:49 PM: warning gatsby-plugin-feed was initialized in gatsby-config.js without a feeds option.
5:43:49 PM: This means that the plugin will use the internal RSS feed creation, which may not match your use case.
5:43:49 PM: This behavior will be removed in the next major release of gatsby-plugin-feed.
5:43:49 PM: For more info, check out: https://gatsby.dev/adding-rss-feed
5:43:49 PM: success onPreBootstrap - 0.007s
5:43:49 PM: success createSchemaCustomization - 0.184s
5:43:49 PM: error "gatsby-transformer-json" threw an error while running the onCreateNode lifecycle:
5:43:49 PM: Unexpected end of JSON input
5:43:49 PM:   61 |
5:43:49 PM:   62 |   const content = await loadNodeContent(node);
5:43:49 PM: > 63 |   const parsedContent = JSON.parse(content);
5:43:49 PM:      |                              ^
5:43:49 PM:   64 |
5:43:49 PM:   65 |   if (_.isArray(parsedContent)) {
5:43:49 PM:   66 |     parsedContent.forEach((obj, i) => {
5:43:49 PM: 
5:43:49 PM:   SyntaxError: Unexpected end of JSON input
5:43:49 PM:   
5:43:49 PM:   - JSON.parse
5:43:49 PM:   
5:43:49 PM:   - gatsby-node.js:63 Object.onCreateNode
5:43:49 PM:     [repo]/[gatsby-transformer-json]/gatsby-node.js:63:30
5:43:49 PM:   
5:43:49 PM: 
5:43:49 PM: not finished source and transform nodes - 0.307s
5:43:49 PM: Skipping functions preparation step: no functions directory set
5:43:49 PM: Caching artifacts
5:43:49 PM: Started saving node modules
5:43:49 PM: Finished saving node modules
5:43:49 PM: Started saving pip cache
5:43:50 PM: Finished saving pip cache
5:43:50 PM: Started saving emacs cask dependencies
5:43:50 PM: Finished saving emacs cask dependencies
5:43:50 PM: Started saving maven dependencies
5:43:50 PM: Finished saving maven dependencies
5:43:50 PM: Started saving boot dependencies
5:43:50 PM: Finished saving boot dependencies
5:43:50 PM: Started saving go dependencies
5:43:50 PM: Finished saving go dependencies
5:43:50 PM: Error running command: Build script returned non-zero exit code: 1
5:43:50 PM: Failing build: Failed to build site
5:43:50 PM: failed during stage 'building site': Build script returned non-zero exit code: 1
5:43:50 PM: Finished processing build request in 42.148315473s

Here’s an image to accompany it of the current build settings I have.

I’m not sure what to do to fix this? The github repository by the way, is available for anyone to view and clone if I remember correctly, so you’re free to have a look at all the code. I’ve tried combing through all of my JSON files to see what if anything was wrong, but I could find any errors with any JSON code I wrote (you can find it under /components/portfolio/projects.json)

Can anyone help me out? I really want to get this site up and running, but I can’t find any way to fix the issue at hand.

Appreciate it in advance!

hey there, generally, when things suceed locally but fail on our system it is is either a case sensitivity issue (which doesn’t seem to be the case here) or a version conflict of some dependency.

Can you post your package.json, and also, are you or are you not commiting your package lock file?

Hey Perry,
Here’s my package.json. I’m pretty sure I’m only commuting this. How would I configure it so that the package-lock.json doesn’t commit? I assume it is committing, given that I can see it on my github repo. Is that something I need to add to my .gitignore?

{
  "name": "gatsby-starter-blog",
  "private": true,
  "description": "A starter for a blog powered by Gatsby and Markdown",
  "version": "0.1.0",
  "author": "Kyle Mathews <mathews.kyle@gmail.com>",
  "bugs": {
    "url": "https://github.com/gatsbyjs/gatsby/issues"
  },
  "dependencies": {
    "@babel/plugin-proposal-decorators": "^7.8.3",
    "bootstrap": "^4.4.1",
    "gatsby": "^2.19.7",
    "gatsby-image": "^2.2.40",
    "gatsby-plugin-feed": "^2.3.26",
    "gatsby-plugin-google-analytics": "^2.1.34",
    "gatsby-plugin-manifest": "^2.2.39",
    "gatsby-plugin-offline": "^3.0.32",
    "gatsby-plugin-react-helmet": "^3.1.21",
    "gatsby-plugin-sharp": "^2.4.5",
    "gatsby-plugin-transition-link": "^1.17.7",
    "gatsby-plugin-typography": "^2.3.21",
    "gatsby-remark-copy-linked-files": "^2.1.36",
    "gatsby-remark-images": "^3.1.42",
    "gatsby-remark-prismjs": "^3.3.30",
    "gatsby-remark-relative-images": "^0.2.3",
    "gatsby-remark-responsive-iframe": "^2.2.31",
    "gatsby-remark-smartypants": "^2.1.20",
    "gatsby-source-filesystem": "^2.1.46",
    "gatsby-transformer-json": "^2.2.26",
    "gatsby-transformer-remark": "^2.6.48",
    "gatsby-transformer-sharp": "^2.3.14",
    "gsap": "^3.2.2",
    "prismjs": "^1.19.0",
    "react": "^16.12.0",
    "react-bootstrap": "^1.0.0-beta.17",
    "react-carousel-slider": "^2.0.13",
    "react-decorators": "^1.2.2",
    "react-dom": "^16.12.0",
    "react-helmet": "^5.2.1",
    "react-reveal": "^1.2.2",
    "react-slick": "^0.25.2",
    "react-text-loop": "^2.3.0",
    "react-typography": "^0.16.19",
    "slick-carousel": "^1.8.1",
    "typed.js": "^2.0.11",
    "typeface-merriweather": "0.0.72",
    "typeface-montserrat": "0.0.75",
    "typography": "^0.16.19",
    "typography-theme-wordpress-2016": "^0.16.19"
  },
  "devDependencies": {
    "@babel/core": "^7.8.7",
    "@babel/preset-env": "^7.8.7",
    "babel-preset-gatsby": "^0.2.31",
    "prettier": "^1.19.1"
  },
  "homepage": "https://github.com/gatsbyjs/gatsby-starter-blog#readme",
  "keywords": [
    "gatsby"
  ],
  "license": "MIT",
  "main": "n/a",
  "repository": {
    "type": "git",
    "url": "git+https://github.com/gatsbyjs/gatsby-starter-blog.git"
  },
  "scripts": {
    "build": "gatsby build",
    "develop": "gatsby develop",
    "format": "prettier --write \"**/*.{js,jsx,json,md}\"",
    "start": "npm run develop",
    "serve": "gatsby serve",
    "clean": "gatsby clean",
    "test": "echo \"Write tests! -> https://gatsby.dev/unit-testing\" && exit 1"
  }
}

Edit: Had tonnes of trouble getting it to format.

so, looking at your package.json i do see that some of these packages are a little out of date. For example, gatsby-transformer-json current version is 2.4.0:

also there have been newer versions of gatsby etc released since then. I’m going to make an educated guess that the problem you are seeing is due to some minor version incompatability.

what you might try is to commit your local package lock that you know works, and then clear cache & redeploy. the netlify system should respect the exact minor versions that are specified in the lock file that are known to work (as opposed to grabbing the versions indicated in the package.json. in a perfect world, all minor versions would always play nice and there would be no weird conflicts. that is not the world we live in, so the lock file “locks” a specific config that is known to work.)

it’s important to clear the cache tho so we don’t end up with a half-updated set of dependencies when you deploy.

let me know how it goes.

just in case, here is the other issue that sometimes pops up when deploying but not locally, but as i said, i don’t think thats your issue, but i have definitely been wrong before:

I’ve checked my repo. The package-lock has always been committed, so I’m not sure why it’s spewing errors. The same package lock that worked on my local system. Or at least, the file was committed when I uploaded the working project. Maybe it uploaded but didn’t actually update? Although I doubt that could happen. I’ve just tried comparing the lock on the git repo and the one on my device, and they’re identical.

Cleared cache, redeployed and…

10:36:29 PM: Build ready to start
10:36:31 PM: build-image version: 2dbd444fcdce00cf06325060a8238d5ae3e86774
10:36:31 PM: build-image tag: v3.3.7
10:36:31 PM: buildbot version: d305548225ac57bb00eb5a596b0b8674e76a4681
10:36:31 PM: Fetching cached dependencies
10:36:31 PM: Starting to download cache of 254.9KB
10:36:31 PM: Finished downloading cache in 75.158171ms
10:36:31 PM: Starting to extract cache
10:36:31 PM: Failed to fetch cache, continuing with build
10:36:31 PM: Starting to prepare the repo for build
10:36:31 PM: No cached dependencies found. Cloning fresh repo
10:36:31 PM: git clone https://github.com/TonyIngall/gatsby-portfolio
10:36:33 PM: Preparing Git Reference refs/heads/master
10:36:34 PM: Starting build script
10:36:34 PM: Installing dependencies
10:36:35 PM: Downloading and installing node v10.20.1...
10:36:35 PM: Downloading https://nodejs.org/dist/v10.20.1/node-v10.20.1-linux-x64.tar.xz...
10:36:36 PM: 
####################################
10:36:36 PM:                            50.4%
10:36:36 PM: 
####################################################
10:36:36 PM: #################### 100.0%
10:36:36 PM: Computing checksum with sha256sum
10:36:36 PM: Checksums matched!
10:36:38 PM: Now using node v10.20.1 (npm v6.14.4)
10:36:39 PM: Attempting ruby version 2.6.2, read from environment
10:36:40 PM: Using ruby version 2.6.2
10:36:40 PM: Using PHP version 5.6
10:36:40 PM: Started restoring cached node modules
10:36:40 PM: Finished restoring cached node modules
10:36:40 PM: Installing NPM modules using NPM version 6.14.4
10:37:25 PM: > sharp@0.23.4 install /opt/build/repo/node_modules/sharp
10:37:25 PM: > (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
10:37:25 PM: info
10:37:25 PM: sharp
10:37:25 PM:  Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.8.1/libvips-8.8.1-linux-x64.tar.gz
10:37:28 PM: > core-js@2.6.11 postinstall /opt/build/repo/node_modules/core-js
10:37:28 PM: > node -e "try{require('./postinstall')}catch(e){}"
10:37:28 PM: Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
10:37:28 PM: The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: 
10:37:28 PM: > https://opencollective.com/core-js 
10:37:28 PM: > https://www.patreon.com/zloirock 
10:37:28 PM: Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
10:37:28 PM: > core-js-pure@3.6.4 postinstall /opt/build/repo/node_modules/core-js-pure
10:37:28 PM: > node -e "try{require('./postinstall')}catch(e){}"
10:37:29 PM: > gatsby-telemetry@1.1.47 postinstall /opt/build/repo/node_modules/gatsby-telemetry
10:37:29 PM: > node src/postinstall.js || true
10:37:29 PM: > cwebp-bin@5.1.0 postinstall /opt/build/repo/node_modules/cwebp-bin
10:37:29 PM: > node lib/install.js
10:37:29 PM:   ✔ cwebp pre-build test passed successfully
10:37:29 PM: > mozjpeg@6.0.1 postinstall /opt/build/repo/node_modules/mozjpeg
10:37:29 PM: > node lib/install.js
10:37:30 PM:   ✔ mozjpeg pre-build test passed successfully
10:37:30 PM: > pngquant-bin@5.0.2 postinstall /opt/build/repo/node_modules/pngquant-bin
10:37:30 PM: > node lib/install.js
10:37:30 PM:   ✔ pngquant pre-build test passed successfully
10:37:30 PM: > gatsby-cli@2.8.27 postinstall /opt/build/repo/node_modules/gatsby/node_modules/gatsby-cli
10:37:30 PM: > node scripts/postinstall.js
10:37:30 PM: > gatsby@2.19.7 postinstall /opt/build/repo/node_modules/gatsby
10:37:30 PM: > node scripts/postinstall.js
10:37:34 PM: npm
10:37:34 PM:  WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules/fsevents):
10:37:34 PM: npm WARN notsup
10:37:34 PM:  SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
10:37:34 PM: npm WARN optional
10:37:34 PM:  SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/chokidar/node_modules/fsevents):
10:37:34 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
10:37:34 PM: added 2270 packages from 1111 contributors and audited 30130 packages in 52.161s
10:37:37 PM: 74 packages are looking for funding
10:37:37 PM:   run `npm fund` for details
10:37:37 PM: found 86 vulnerabilities (75 low, 2 moderate, 9 high)
10:37:37 PM:   run `npm audit fix` to fix them, or `npm audit` for details
10:37:37 PM: NPM modules installed
10:37:37 PM: Started restoring cached go cache
10:37:37 PM: Finished restoring cached go cache
10:37:37 PM: unset GOOS;
10:37:37 PM: unset GOARCH;
10:37:37 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64';
10:37:37 PM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}";
10:37:37 PM: go version >&2;
10:37:37 PM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.12.linux.amd64.env';
10:37:37 PM: go version go1.12 linux/amd64
10:37:37 PM: Installing missing commands
10:37:37 PM: Verify run directory
10:37:37 PM: Executing user command: gatsby build
10:37:40 PM: success open and validate gatsby-configs - 0.078s
10:37:41 PM: success load plugins - 1.085s
10:37:41 PM: warning The Google Analytics plugin requires a tracking ID. Did you mean to add it?
10:37:41 PM: success onPreInit - 0.010s
10:37:41 PM: success delete html and css files from previous builds - 0.013s
10:37:41 PM: success initialize cache - 0.010s
10:37:41 PM: success copy gatsby files - 0.033s
10:37:41 PM: warning gatsby-plugin-feed was initialized in gatsby-config.js without a feeds option.
10:37:41 PM: This means that the plugin will use the internal RSS feed creation, which may not match your use case.
10:37:41 PM: This behavior will be removed in the next major release of gatsby-plugin-feed.
10:37:41 PM: For more info, check out: https://gatsby.dev/adding-rss-feed
10:37:41 PM: success onPreBootstrap - 0.007s
10:37:41 PM: success createSchemaCustomization - 0.179s
10:37:42 PM: error "gatsby-transformer-json" threw an error while running the onCreateNode lifecycle:
10:37:42 PM: Unexpected end of JSON input
10:37:42 PM:   61 |
10:37:42 PM:   62 |   const content = await loadNodeContent(node);
10:37:42 PM: > 63 |   const parsedContent = JSON.parse(content);
10:37:42 PM:      |                              ^
10:37:42 PM:   64 |
10:37:42 PM:   65 |   if (_.isArray(parsedContent)) {
10:37:42 PM:   66 |     parsedContent.forEach((obj, i) => {
10:37:42 PM: 
10:37:42 PM:   SyntaxError: Unexpected end of JSON input
10:37:42 PM:   
10:37:42 PM:   - JSON.parse
10:37:42 PM:   
10:37:42 PM:   - gatsby-node.js:63 Object.onCreateNode
10:37:42 PM:     [repo]/[gatsby-transformer-json]/gatsby-node.js:63:30
10:37:42 PM:   
10:37:42 PM: 
10:37:42 PM: not finished source and transform nodes - 0.393s
10:37:42 PM: Skipping functions preparation step: no functions directory set
10:37:42 PM: Caching artifacts
10:37:42 PM: Started saving node modules
10:37:42 PM: Finished saving node modules
10:37:42 PM: Started saving pip cache
10:37:42 PM: Finished saving pip cache
10:37:42 PM: Started saving emacs cask dependencies
10:37:42 PM: Finished saving emacs cask dependencies
10:37:42 PM: Started saving maven dependencies
10:37:42 PM: Finished saving maven dependencies
10:37:42 PM: Started saving boot dependencies
10:37:42 PM: Finished saving boot dependencies
10:37:42 PM: Started saving go dependencies
10:37:42 PM: Finished saving go dependencies
10:37:46 PM: Error running command: Build script returned non-zero exit code: 1
10:37:46 PM: Failing build: Failed to build site
10:37:46 PM: failed during stage 'building site': Build script returned non-zero exit code: 1
10:37:47 PM: Finished processing build request in 1m15.783440162s

The exact same issue. I doubt it’s a case sensitivity issue, because the error is nothing to do with a missing file. It’s an “unexpected end of JSON input”. Although like I said, I’ve gone over my one JSON file which looks a bit like this:

[
    {
        "title": "Project2020",
        "slug": "project2020",
        "url": "https://beta.project2020.co.uk/",
        "image": "./images/project2020.jpg",
        "description": "Website done for a music group, including a custom media player.",
        "date": "2019-10-21T13:37:27+00:00"
    }
]

And I assume, that this code is fine since it works locally.

Really don’t understand what’s going on here. I just cloned a Gatsby Starter, and worked from there. Would updating the dependencies be a good idea? Or would that just make things worse?

yeah, i think that updating the dependencies is a good next step.

i would update them locally, npm update confirm that everything is working as expected locally (dont miss that step!), commit, push, and see if that fixes things.

I updated the dependencies! Now at least I’m able to replicate the problem locally. Now it’s just a case of figuring out what the actual issue is. To be fair, I don’t actually create pages from a JSON file. Although I do have a JSON file with no issues in it, so I’m not entirely sure what’s causing the issue.

I guess that puts me a little closer to success though, not sure what more can be suggested?

Edit: Most of the issues I can find on Github involve finding a randomly hidden empty JSON file… Not sure how to effectively scower for that without spending hours going through sub folders.

hmm. maybe i’m missing something but do you need that dependency, then?

I mean, given that I’m transforming JSON files by having the info read into generated elements, I assume so. But it’s just all acting up. Really can’t figure out why it’s happening.

yeah, sounds like you do need it.

given that the issue is also occurring locally, i’m not sure how helpful we can be, in all honesty. You might have better luck chatting with the gatsby folks about this, maybe they have some answers for you?

I’m sorry we don’t have better news :confused:

That’s fine no worries! You’ve been great help! Being able to replicate it on my local system means that I know it’s not a server side issue. Well, unless the package-lock isn’t doing its job for some reason. I’ve started chatting to Gatsby people. Currently don’t have any results, but hopefully I’ll get some soon!

Either way, really appreciate it guys!
Thanks a lot!

you’re welcome! if you find a solution, please do share it here for other folks!

The solution is a little complicated. But, I have run into a Netlify issue so, I guess I’m back here. I’ll make it into a new thread though, don’t want to make this one off topic!

Here it is if you wan’t to follow the saga

1 Like