Hi, @proton. When I tried to build the site locally I get this error:
$ GATSBY_EXPERIMENTAL_PAGE_BUILD_ON_DATA_CHANGES=true gatsby build --log-pages
╔════════════════════════════════════════════════════════════════════════╗
║ ║
║ Gatsby collects anonymous usage analytics ║
║ to help improve Gatsby for all users. ║
║ ║
║ If you'd like to opt-out, you can use `gatsby telemetry --disable` ║
║ To learn more, checkout https://gatsby.dev/telemetry ║
║ ║
╚════════════════════════════════════════════════════════════════════════╝
success open and validate gatsby-configs, load plugins - 1.243s
info [@imgix/gatsby] Loaded plugin.
success onPreInit - 0.049s
success initialize cache - 0.024s
success copy gatsby files - 0.070s
success Compiling Gatsby Functions - 0.351s
success onPreBootstrap - 0.381s
success gatsby-source-prismic - create types - 0.021s
ERROR
[@imgix/gatsby] Fatal error during setup: Error: The plugin config is not in the correct format. Errors: Invalid value undefined supplied to :
GatsbySourceUrlOptions/domain: string
not finished createSchemaCustomization - 0.082s
error Command failed with exit code 1.
I also notices that you are using a number of environment variables for the build at Netlify. Do weed need to enable those environment variable locally and at Netlify to test this? If so, do we have your permission to reused the environment variables for affectionate-curie-46aff8 when we test?
If not, how do you recommend we test this site build? What is required to get it to build successfully?
Hi @proton , thank you for creating and sharing the new repo with us! We really appreciate it While Luke works on building the site locally I wanted to check on a few things.
Firstly, in our audit logs, I see you uninstalled netlify-plugin-gatsby-cache and installed @netlify/plugin-gatsby on Aug 6. I looked thru your deploy logs since that time and had trouble finding a build log that had netlify-plugin-gatsby-cache installed. Can you share the deploy ID where you see both plugins installed?
Secondly, good hunch for removing the Gatsby incremental build feature! Can you please also try changing the build command to env && <your usual build command>? This will confirm the removal in the build log for us.
I don’t think there’s any evidence of both plugins being installed simultaneously in Netlify’s build environment after I switched them . However, it does happen when building locally using Netlify CLI.
For the reproduction repo that I made, only the one plugin is loading - which is correct - when building using Netlify CLI.
Apologies, I’m somewhat of a novice when it comes to constructing build scripts. Do you mean in the Netlify UI that you want the build command to be something like yarn env && build?
For the build command, when you execute the build locally can you try using the command env && netlify build That will generate output in the build log and tell us if the Gatsby incremental build feature was indeed removed.
I forked your repo and I’m working on building locally to test as well!
It’s tricky because this is using Prismic, to be honest. And, I think that that is where the issue lies, personally. It’s the only thing we don’t have visibility over and nothing else which I can see appears to be awry.
I’ve checked the repro’s deploy and the pages specified are deleted (e.g. /blog/easily-understand-how-to-stop-procrastinating doesn’t exist). But, this is what the build is being told by Prismic?
If this was reproducible without Prismic, then I’d be inclined to say that this is a failing of the build system. Otherwise, I think this may need input from the gatsby-source-prismic maintainer(s).
While Luke works on building the site locally I wanted to check on a few things.