Closed nickreese closed 5 years ago
Just to verify, I deployed some site on Netlify and gatsby-node worked there - but this was using some vanilla options.
There is potential that there were some errors that until recently Gatsby would silently swallow so users wouldn't be notified about (it was fixed in gatsby@2.3.26
- so please try bumping to this one and see if there is any new insight showing)
If this does not help, I don't think of anything and probably won't be able to debug without access to reproduction.
@Pieh — Got it building again for our deadline.
Will confirm what the root cause was once we sort it out. The fix was either upgrading our packages as you mentioned or resolving a conflict between two plugins. Will confirm tomorrow when back in the office so see if I can get it to fail with the plugin conflict.
Plugin conflict doesn’t make sense because it wasn’t building without ANY plugins but that was part of the same commit as upgrading dependencies so will look closer.
@pieh — We were unable to reproduce the issue when enabling both plugins. Our team believes it was fixed by upgrading our packages including gatsby.
Summary
We've had a gatsby install running on netlify.com for almost 2 months with no issues. In the last few days, their build process has stopped reading our gatsby-node.js file as evidenced by this simple console.log not getting printed in the build information.
To troubleshoot we’ve downloaded the netlify build image and can confirm the build completes as expected. To make sure it wasn’t env variables causing the issue we’ve also passed in all of the exact same env variables into this build.
The build process works with
gatsby build
locally as well.We've tried everything and we've contacted their support who seem to have no idea why this would be happening.
All of this said, are there any specific situations where gatsby-node.js wouldn't be run by gatsby?
Relevant information
Things we've tried:
Environment (if relevant)
Netlify's build process. Gatsby-config does run, we can see the console.logs of that.
File contents (if changed)
gatsby-config.js
:package.json
:gatsby-node.js
:gatsby-browser.js
: N/Agatsby-ssr.js
: N/A