-
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
[v2] Support Graphql queries in npm package / node_modules #4322
Comments
I think this is a great idea! We'd need to evaluate how to do this in a performant way but it seems doable. I'm not going to make this a blocker for v2's release (it can go in at any time since it's not a breaking change) but would love someone to investigate the implications of doing this & make a PR if they'd like. |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! Thanks for being a part of the Gatsby community! 💪💜 |
fixed by #15284 |
@LekoArts not 100% sure but i think this broke my app. I use the plugin gatsby-plugin-mailchimp and in there are two example folders for the implementation of the plugin in v1 and v2. both have a file where they use a query named SiteTitleQuery. And since a few days my app does throw a error during build and dev:
|
How can i prevent gatsby from extracting those queries now? |
As another layer of abstraction, it would be great to support templates and/or graphql fragments in npm packages as originally noted here in #2662 . This would require extracting graphql queries from node_modules. The low hanging fruit is to support extracting queries from any "components" specified in
createPage
, but eventually supporting fragments would be nice as well.Tangentially related is that gatsby would need to babel templates as well to deal with the graphql queries nicely. This is already planned in #3870 5).
The text was updated successfully, but these errors were encountered: