Builds fail: "Built Rendering Engines failed validation failed validation."
See original GitHub issuePreliminary Checks
- This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
- This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions
Description
I’m helping test a new gatsby-source-prismic plugin with @angeloashmore and am running into this error message when building my site. We are 90% sure this is related to the 6.0.0-alpha.10 version of the plugin, but we are unsure what exactly is breaking on Gatsby’s side.
Reproduction Link
https://github.com/jared-mcc/GatsbyErrorMinimalReproduction/settings
Steps to Reproduce
- Clone the project
- npm install
- npm run build
Expected Result
A successful build.
Actual Result
We receive the following error message:
“Built Rendering Engines failed validation failed validation. Please open an issue with a reproduction at https://github.com/gatsbyjs/gatsby/issues/new for more help”
Environment
System:
OS: macOS 12.4
CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 14.16.0 - ~/.nvm/versions/node/v14.16.0/bin/node
Yarn: 1.22.11 - ~/.nvm/versions/node/v14.16.0/bin/yarn
npm: 7.13.0 - ~/.nvm/versions/node/v14.16.0/bin/npm
Browsers:
Chrome: 104.0.5112.101
Safari: 15.5
npmPackages:
gatsby: ^4.21.1 => 4.22.0
gatsby-plugin-gatsby-cloud: ^4.21.0 => 4.22.0
gatsby-plugin-image: ^2.21.0 => 2.22.0
gatsby-plugin-manifest: ^4.21.0 => 4.22.0
gatsby-plugin-offline: ^5.6.0 => 5.22.0
gatsby-plugin-prismic-previews: ^6.0.0-alpha.10 => 6.0.0-alpha.11
gatsby-plugin-react-helmet: ^5.6.0 => 5.22.0
gatsby-plugin-sass: ^5.6.0 => 5.22.0
gatsby-plugin-sharp: ^4.21.0 => 4.22.0
gatsby-source-filesystem: ^4.21.1 => 4.22.0
gatsby-source-prismic: ^6.0.0-alpha.10 => 6.0.0-alpha.11
gatsby-transformer-sharp: ^4.21.0 => 4.22.0
npmGlobalPackages:
gatsby-cli: 4.21.0
Config Flags
No response
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Unexpected Rendering Engines validation failure (Gatsby v4)
After migrating to Gatsby v4, build fails with: failed Validating Rendering Engines - 0.641s ERROR #98001 WEBPACK Built Rendering Engines ...
Read more >Rendering Engines Fail Error : r/gatsbyjs - Reddit
Built Rendering Engines failed validation failed validation. Error: Generated engines use disallowed import "node-gyp-build". Only allowed ...
Read more >Why my gatsby build failed on Error: ENOENT: no such file or ...
109s ERROR #98001 WEBPACK Built Rendering Engines failed validation failed validation. Please open an issue with a reproduction at https:// ...
Read more >Build gives webpack error 98001. Generated engines use ...
ERROR #98001 WEBPACK. Built Rendering Engines failed validation failed validation. ... Error: Generated engines use disallowed import "node-gyp-build".
Read more >Troubleshooting build errors | Cloud Build Documentation
Build trigger fails due to missing cloudbuild.builds.create permission ... Build triggers use the Cloud Build service account to create a build. The error...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@jared-mcc @angeloashmore I started https://github.com/gatsbyjs/gatsby/pull/36506 which seems to fix this for me on the repro you provided.
@angeloashmore @jared-mcc For now I released
@next
with the change (gatsby@4.23.0-next.2
) so at least you could test those things out on your end, but we will look to release this in stable next week most likely