Gatsby builds only failing on Netlify

[fool]

Hi @Chalarangelo! While we can’t help with your source code in depth, this article describes how you can debug and some things you should try, especially around syncing versions between netlify and your local, and watching out for some things like case sensitive filesystems (I see some capital letters in your error: 6:25:35 PM: Snippet.html provided incorrect OutputType: 'Object({ resolve: [function resolve] })' that might be a contributing factor):

[Support Guide] Debugging Netlify site builds

Last reviewed by Netlify Support - August, 2023 Note: This article is only about builds within Netlify’s Continuous Integration (CI) environment, as triggered from git commits or from incoming build webhooks. You can learn more in depth about how Netlify builds your site in this article about how our build bots build sites. Some background There are a fair number of reasons that a build could fail in Netlify’s CI environment, even if building works locally. Testing locally is always the place …

Take a look through there and hopefully you’ll find an answer. If not, you could try printing the error log after build, by using a build command like this:

npm run build ; cat /opt/buildhome/.npm/_logs/2019-*debug.log ; sleep 120 ; false

That will:

1. run your build
2. even if it fails, send the log file if it exists
3. wait 2 minutes to finish logging that output file
4. make sure we don’t publish a broken build.

You’ll have to undo that setting once you’ve understood and hopefully fixed the error since your site will never publish with that build command (you can restore to plain npm run build once fixed)