-
Notifications
You must be signed in to change notification settings - Fork 1.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
Include @graphql-codegen/client-preset in @graphql-codegen/cli by default #9601
Conversation
🦋 Changeset detectedLatest commit: d29094c The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
diff --git a/website/algolia-lockfile.json b/website/algolia-lockfile.json
index 4a8d4b81a..0a8974dac 100644
--- a/website/algolia-lockfile.json
+++ b/website/algolia-lockfile.json
@@ -913,7 +913,7 @@
"anchor": "setup"
}
],
- "content": "2c4dd42cec4906229f4594ede093a8d8",
+ "content": "daa62b8fb6719b45975db3ffb56abdbd",
"url": "https://www.the-guild.dev/graphql/codegen/docs/getting-started/installation",
"domain": "https://www.the-guild.dev/graphql/codegen",
"hierarchy": [ |
🚀 Snapshot Release (
|
Package | Version | Info |
---|---|---|
@graphql-codegen/cli |
5.0.1-alpha-20231019221049-f2a3ec403 |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/core |
4.0.1-alpha-20231019221049-f2a3ec403 |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/add |
5.0.1-alpha-20231019221049-f2a3ec403 |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/fragment-matcher |
5.0.1-alpha-20231019221049-f2a3ec403 |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/introspection |
4.0.1-alpha-20231019221049-f2a3ec403 |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/schema-ast |
4.0.1-alpha-20231019221049-f2a3ec403 |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/visitor-plugin-common |
4.0.2-alpha-20231019221049-f2a3ec403 |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/typescript-document-nodes |
4.0.2-alpha-20231019221049-f2a3ec403 |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/gql-tag-operations |
4.0.2-alpha-20231019221049-f2a3ec403 |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/typescript-operations |
4.0.2-alpha-20231019221049-f2a3ec403 |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/typescript-resolvers |
4.0.2-alpha-20231019221049-f2a3ec403 |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/typed-document-node |
5.0.2-alpha-20231019221049-f2a3ec403 |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/typescript |
4.0.2-alpha-20231019221049-f2a3ec403 |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/client-preset |
4.2.0-alpha-20231019221049-f2a3ec403 |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/graphql-modules-preset |
4.0.2-alpha-20231019221049-f2a3ec403 |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/testing |
3.0.1-alpha-20231019221049-f2a3ec403 |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/plugin-helpers |
5.0.2-alpha-20231019221049-f2a3ec403 |
npm ↗︎ unpkg ↗︎ |
💻 Website PreviewThe latest changes are available as preview in: https://48ac85b3.graphql-code-generator.pages.dev |
can you please rebase this one @beerose |
Done @saihaj. Am I free to merge it now, or do we want to wait with this change? |
🚨 IMPORTANT: Please do not create a Pull Request without creating an issue first.
Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Related # (issue)
Type of change
Please delete options that are not relevant.
Screenshots/Sandbox (if appropriate/relevant):
Adding links to sandbox or providing screenshots can help us understand more about this PR and take action on it as appropriate
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Test Environment:
@graphql-codegen/...
:Checklist:
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...