chore(deps): update graphqlcodegenerator monorepo (major) #200
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: unboundsoftware/schemas-app#200
Reference in New Issue
Block a user
This PR contains the following updates:
6.3.1→7.0.06.1.8→7.0.05.0.10→6.0.05.1.0→6.0.0Release 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/typed-document-node)
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
Patch Changes
#10496
afaace6Thanks @eddeee888! - dependencies updates:
auto-bind@^5.0.0↗︎ (from~4.0.0, independencies)change-case-all@^2.1.0↗︎ (from1.0.15, independencies)#10496
afaace6Thanks @eddeee888! - dependencies updates:
change-case-all@^2.1.0↗︎ (from1.0.15, independencies)auto-bind@^5.0.0↗︎ (from~4.0.0, independencies)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]:dotansimha/graphql-code-generator (@graphql-codegen/typescript)
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]:dotansimha/graphql-code-generator (@graphql-codegen/typescript-operations)
v6.0.0Compare Source
Major Changes
#10496
afaace6Thanks @eddeee888! - Fix nullable field optionality in operations
Previously, a nullable Result field is generated as optional (marked by
?TypeScript modifier)by default. This is not correct, because generally at runtime such field can only be
null, andnot
undefined(both missing from the object ORundefined). The only exceptions are when fieldsare deferred (using
@deferdirective) or marked as conditional (using@skipor@include).Now, a nullable Result field cannot be optional unless the exceptions are met. This also limits
avoidOptionalsto only target Variables input, since some users may want to force explicitnullwhen providing operation variables.#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: typescript-operations plugin
now generates enum if it is used in operation.
#10496
afaace6Thanks @eddeee888! - Conditionally generate input types and output
enums into target file
#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: Decouple
typescript-operationsplugin fromtypescriptpluginPreviously,
TypeScriptOperationVariablesToObjectfromtypescript-operationswas extending fromtypescriptplugin. This made it (1) very hard to read, as we need to jump from base class <->typescript class <-> typescript-operations class to understand the flow and (2) very hard to
evolve the two independently (which is the point of this work).
Since there's not much shared logic anyways, it's simpler to extend the
typescript-operationsclass from the base class directly.
#10496
afaace6Thanks @eddeee888! - The
typescript-operationsplugin no longergenerates InputMaybe and Scalars types; it now uses native Typescript types instead.
#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: Operation plugin and Client
Preset no longer generates optional
__typenamefor result type__typenamshould not be in the request unless:Note: Apollo Client users can still use
nonOptionalTypename: trueandskipTypeNameForRoot: trueto ensure generated types match the runtime behaviour.#10496
afaace6Thanks @eddeee888! - Integrate new typescript-operations into
client-preset
#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: config.avoidOptionals now
only supports object, inputValue, defaultValue
#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: rename avoidOptionals.object
to avoidOptionals.variableValue
Minor Changes
#10496
afaace6Thanks @eddeee888! - Add support for declarationKind for
typescript-operations
typeorinterfacetypebecause it's an alias e.g.Variables = Exact<{ something: type }>typeorinterfaceextractAllFieldsToTypes:trueorextractAllFieldsToTypesCompact:true, Resultsare used as type alias, so they are forced to be
type. There is a console warning for users.#10496
afaace6Thanks @eddeee888! - Add importSchemaTypesFrom support
#10496
afaace6Thanks @eddeee888! - Add generateOperationTypes to
typescript-operations to allow omitting operation types such as Variables,
Query/Mutation/Subscription selection set, and Fragment types
#10496
afaace6Thanks @eddeee888! - Fixing 2 bugs: 1) including enums from
external fragments; 2) extractAllFieldsToTypesCompact does not create duplicates
Patch Changes
#10496
afaace6Thanks @eddeee888! - dependencies updates:
auto-bind@^5.0.0↗︎ (from~4.0.0, independencies)@graphql-codegen/schema-ast@^5.0.1↗︎(to
dependencies)@graphql-codegen/typescript@^5.0.10↗︎(from
dependencies)#10496
afaace6Thanks @eddeee888! - dependencies updates:
@graphql-codegen/schema-ast@^5.0.0↗︎(to
dependencies)#10496
afaace6Thanks @eddeee888! - dependencies updates:
@graphql-codegen/typescript@^5.0.7↗︎(from
dependencies)#10496
afaace6Thanks @eddeee888! - dependencies updates:
auto-bind@^5.0.0↗︎ (from~4.0.0, independencies)#10496
afaace6Thanks @eddeee888! - Improve
namespacedImportNameusability bysetting a default when
importSchemaTypesFromis set#10496
afaace6Thanks @eddeee888! - Add internal utility type warning to deter
usage
#10496
afaace6Thanks @eddeee888! - Add
printTypeScriptMaybeTypeto handleprinting TS types, as there are special cases like
anyandunknown#10496
afaace6Thanks @eddeee888! - Re-implement inputMaybeValue
#10496
afaace6Thanks @eddeee888! - Only generate
Exactutility type at the topif it is used
Exactutility is only used to wrap variables types for operations (queries, mutations andsubscriptions) if they exist in the document.
Exactis never used when there are onlyfragments.
This is important to conditionally generate as users may use very strict tsconfig that will fail
compiling if there are unused types.
#10496
afaace6Thanks @eddeee888! - Fix external custom scalars not getting
imported
#10496
afaace6Thanks @eddeee888! - Ensure Input and Variables use the same input
scalars default e.g.
IDcan takestring | number#10496
afaace6Thanks @eddeee888! - Fix
@skipand@includenot applyingconditional modifiers correctly when used on inline fragment
#10496
afaace6Thanks @eddeee888! - Abstract how enum imports are generated into
visitor-plugin-common package
#10496
afaace6Thanks @eddeee888! - Fix
@skipand@includenot applyingconditional modifiers correctly when used on fragment sread, and
@deferfragments#10496
afaace6Thanks @eddeee888! - Fix importing issue of Input when
importSchemaTypesFrom is used
#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: (UTC)
🚦 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 has been generated by Mend Renovate.