-
Notifications
You must be signed in to change notification settings - Fork 922
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@builder.io/gatsby support v4 #719
Comments
My case, the plugin doesn't fail, but I can't query
|
Even after
Here's the
|
Thanks for the detailed report @gavlyin , working on a solution, it'd help if you have a repo with a reproduction, I'll try to reproduce on my own as well. |
@teleaziz Thanks. Please ping me if you want any help. |
Should be fixed with #762 |
@codercatdev That worked. Thanks! |
I am still seeing this warning though!
|
@gavlyin I just released a new major version try:
|
Just a heads up, after installing the latest on my project that I'm attempting to update to Gatsby 4, which happens to also use Sounds like its been a long standing issue among other plugins too: However, taking a peak at the source code, I think you can get away pretty easily by changing this value: I created a diff --git a/node_modules/@builder.io/gatsby/gatsby-node.js b/node_modules/@builder.io/gatsby/gatsby-node.js
index 60b7a48..cf7128c 100644
--- a/node_modules/@builder.io/gatsby/gatsby-node.js
+++ b/node_modules/@builder.io/gatsby/gatsby-node.js
@@ -320,7 +320,7 @@ function createSchemaNode({
parent: null,
children: [],
internal: {
- type: `GraphQLSource`,
+ type: `BuilderGraphQLSource`,
contentDigest: nodeContentDigest,
ignoreType: true
} which I can confirm bypasses the issue originally met and successfully builds the site as expected. |
@Ash-Matter , addressed the conflict in 3.0.1, thanks so much for the detailed report and the fix |
When installing on new Gatsby the plugin fails because of version support.
The text was updated successfully, but these errors were encountered: