chore(deps): update graphqlcodegenerator monorepo (major)#993
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update graphqlcodegenerator monorepo (major)#993renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
6b3121d to
31901eb
Compare
86400b4 to
51fb7e9
Compare
770c278 to
c4e8cbe
Compare
c4e8cbe to
591aba1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.3.1→7.0.05.0.10→6.0.1Release Notes
dotansimha/graphql-code-generator (@graphql-codegen/cli)
v7.0.0Compare Source
Major Changes
#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: Update deps to latest, some
only support ESM
Node 20 support is dropped in this release. Node 22 comes with
require()support for ESM, whichmeans it's easier to integrate ES modules into applications. Therefore, it is safe to start using
ESM-only packages.
If you are a user, please upgrade to Node 22. If you are a lib maintainer and see ESM vs CJS
issues when running Jest tests, try using Vitest.
#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: Drop Node 20 support
#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: Set
noSilentErrors: trueby default
When multiple files match documents pattern, and there are syntax errors in some but not others,
then the operations with errors are not included in the loaded documents list by default
(
noSilentErrors: false). This is annoying for users as there is no feedback loop duringdevelopment.
noSilentErrors: trueis used as the default for Codegen users to make the feedback loop faster.It can still overriden in Codegen Config if desired.
Patch Changes
#10496
afaace6Thanks @eddeee888! - dependencies updates:
@inquirer/prompts@^8.3.2↗︎ (from^7.8.2, independencies)chalk@^5.6.0↗︎ (from^4.1.0, independencies)debounce@^3.0.0↗︎ (from^2.0.0, independencies)detect-indent@^7.0.0↗︎ (from^6.0.0,in
dependencies)listr2@​^10.2.1↗︎ (from^9.0.0, independencies)log-symbols@^7.0.0↗︎(from
^4.0.0, independencies)ts-log@^3.0.0↗︎ (from^2.2.3, independencies)yargs@^18.0.0↗︎ (from^17.0.0, independencies)#10496
afaace6Thanks @eddeee888! - dependencies updates:
chalk@^5.6.0↗︎ (from^4.1.0, independencies)debounce@^3.0.0↗︎ (from^2.0.0, independencies)detect-indent@^7.0.0↗︎ (from^6.0.0,in
dependencies)listr2@​^10.2.1↗︎ (from^9.0.0, independencies)log-symbols@^7.0.0↗︎(from
^4.0.0, independencies)ts-log@^3.0.0↗︎ (from^2.2.3, independencies)yargs@^18.0.0↗︎ (from^17.0.0, independencies)#10496
afaace6Thanks @eddeee888! - dependencies updates:
@inquirer/prompts@^8.3.2↗︎ (from^7.8.2, independencies)#10496
afaace6Thanks @eddeee888! - Use ESM for CLI instead of CJS;
For backwards compatibility;
graphql-codegen-esmis reserved, and alsographql-codegen-cjsisadded for users who want to use CJS.
So the commands are;
graphql-codegen- ESM version, defaultgraphql-codegen-esm- ESM version, same as above, but reserved for backwards compatibilitygraphql-codegen-cjs- CJS version, for users who want to use CJS, but not recommended for newusers. Will be removed in the future.
gql-gen- ESM version, same asgraphql-codegengraphql-code-generator- ESM version, same asgraphql-codegenandgql-genUpdated dependencies
[
afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6]:dotansimha/graphql-code-generator (@graphql-codegen/typescript)
v6.0.1Compare Source
Patch Changes
c95db26Thanks @renovate! - dependencies updates:
tslib@~2.8.0↗︎ (from~2.6.0, independencies)[
5f035cb]:v6.0.0Compare Source
Major Changes
#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: visitors' config option are
moved based on their use case
base-visitor
there
correctly sync the enum type names. This is moved to base visitor
base-visitor there.
Refactors
usages now. The types now extend base-visitor types. This is now consistent with
documents-visitor extending base-visitor
plugin parses configOne, then the types for configOne must be in that class, rather than in
base-documents-visitor
Note: These visitors are rolled up into one type for simplicity
base-visitorbase-documents-visitorandtypescript-operationsvisitorbase-types-visitorandtypescriptvisitorbase-resolvers-visitorandtypescript-resolversvisitor#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: make
unknowninstead ofanythe default custom scalar type#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: Update deps to latest, some
only support ESM
Node 20 support is dropped in this release. Node 22 comes with
require()support for ESM, whichmeans it's easier to integrate ES modules into applications. Therefore, it is safe to start using
ESM-only packages.
If you are a user, please upgrade to Node 22. If you are a lib maintainer and see ESM vs CJS
issues when running Jest tests, try using Vitest.
#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: Drop Node 20 support
#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE:
typescriptplugin nolonger generates
Exactutility type. Instead,typescript-operationsgenerates said utilitytype for every file it creates. This is because it is used only for
Variables, so we only needto generate it once for every generated operation file.
#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: Remove unused utility types
from
typescriptplugin as they were previously used fortypescript-operationsplugin:MakeOptionalMakeMaybeMakeEmptyIncrementalBREAKING CHANGE: Remove
getRootTypeNamesfunction because it's available in@graphql-utils/toolsand not used anywhereMinor Changes
afaace6Thanks @eddeee888! - The
typescript-operationsplugin no longergenerates InputMaybe and Scalars types; it now uses native Typescript types instead.
Patch Changes
#10496
afaace6Thanks @eddeee888! - dependencies updates:
auto-bind@^5.0.0↗︎ (from~4.0.0, independencies)tslib@~2.6.0↗︎ (from^2.8.0, independencies)#10496
afaace6Thanks @eddeee888! - dependencies updates:
auto-bind@^5.0.0↗︎ (from~4.0.0, independencies)#10496
afaace6Thanks @eddeee888! - Extract utilities from base-type-visitor to
be shared with other plugins later: convertSchemaEnumToDeclarationBlockString, getNodeComment
#10496
afaace6Thanks @eddeee888! - Fix namingConvention not being applied
consistently
#10496
afaace6Thanks @eddeee888! - Abstract how enum imports are generated into
visitor-plugin-common package
#10496
afaace6Thanks @eddeee888! - Fix namingConvention not being applied
consistently in imports, Variables, Input and Result
Updated dependencies
[
afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6]:Configuration
📅 Schedule: (in timezone Europe/Rome)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.