-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
feat(gatsby): handle graphql-import-node bundling #36951
Conversation
@@ -110,6 +110,7 @@ | |||
"got": "^11.8.5", | |||
"graphql": "^16.6.0", | |||
"graphql-compose": "^9.0.9", | |||
"graphql-tag": "^2.12.6", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is already being installed transitively (codegen deps eventually install it), so it's not adding new dependency and just makes sure package managers install it in a way that can be resolved from within gatsby
package
@@ -166,6 +166,12 @@ export async function createGraphqlEngineBundle( | |||
test: /\.txt/, | |||
type: `asset/resource`, | |||
}, | |||
{ | |||
test: /\.(graphqls?|gqls?)$/, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is to match const VALID_EXTENSIONS = ['graphql', 'graphqls', 'gql', 'gqls'];
from graphql-import-node
package, so it doesn't exactly match instructions for loader ( https://www.npmjs.com/package/graphql-tag#webpack-loading-and-preprocessing )
(cherry picked from commit d5c775a)
Description
This adds bundling support in case someone is using https://www.npmjs.com/package/graphql-import-node to load queries from
.graphql
files from within gatsby-node file.Without this, engine compilation fails as compilation doesn't know how to handle
.graphql
importsRelated Issues
[ch-56774]