chore(deps): update npm major updates (major) - #1874
Conversation
|
There was a problem hiding this comment.
Pull request overview
Note
Copilot could not run the full agentic suite for this review because it was automatically requested on a bot-authored pull request. Request a review from Copilot under Reviewers to retry with the full agentic suite. Improved support for bot-authored pull requests is coming soon.
Updates toolchain dependencies across apps and packages, primarily focusing on TypeScript and build/type-generation tooling versions.
Changes:
- Bumped
typescriptto7.0.2across multiple workspaces. - Bumped
vite-plugin-dtsto5.0.3across multiple workspaces. - Updated select tooling deps (
@babel/preset-*,@graphql-codegen/*) to newer major versions.
Reviewed changes
Copilot reviewed 12 out of 13 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| packages/url-state-provider/package.json | Bumps TypeScript and vite-plugin-dts for the package toolchain. |
| packages/ui-components/package.json | Bumps Babel presets, TypeScript, and vite-plugin-dts for UI component tooling. |
| packages/template/package.json | Bumps TypeScript and vite-plugin-dts for the template package. |
| packages/oauth/package.json | Bumps TypeScript and vite-plugin-dts for OAuth package tooling. |
| packages/messages-provider/package.json | Bumps TypeScript and vite-plugin-dts for provider package tooling. |
| packages/k8s-client/package.json | Bumps vite-plugin-dts for the client package tooling. |
| packages/greenhouse-auth-provider/package.json | Bumps TypeScript and vite-plugin-dts for auth provider tooling. |
| packages/config/package.json | Bumps TypeScript used by the shared config/tooling package. |
| packages/communicator/package.json | Bumps TypeScript and vite-plugin-dts for communicator package tooling. |
| apps/template/package.json | Bumps TypeScript for the template app tooling. |
| apps/heureka/package.json | Bumps GraphQL codegen plugins and TypeScript for the app toolchain. |
| apps/carbon/package.json | Bumps TypeScript for the app toolchain. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| "typescript": "7.0.2", | ||
| "typescript-eslint": "8.59.4" |
| "typescript": "7.0.2", | ||
| "vite": "8.0.16", | ||
| "vite-plugin-dts": "4.5.4", | ||
| "vite-plugin-dts": "5.0.3", |
|
aff8ebe to
8ff4488
Compare
This PR contains the following updates:
7.29.7→8.0.27.28.5→8.0.15.0.10→6.1.05.1.0→6.1.06.0.3→7.0.24.5.4→5.0.3Release Notes
babel/babel (@babel/preset-env)
v8.0.2Compare Source
🐛 Bug Fix
@babel/coreversion when asserting version in@babel/standalone(@nicolo-ribaudo)babel-helper-validator-identifier🏠 Internal
babel-plugin-proposal-decorators,babel-plugin-transform-regenerator,babel-preset-env@babel/preset-modulesand polyfill packages (@nicolo-ribaudo)v8.0.1Compare Source
💥 Breaking Change
babel-core,babel-plugin-transform-object-rest-spread,babel-plugin-transform-runtime,babel-preset-env,babel-standalonepreset-env'suseBuiltIns(@nicolo-ribaudo)v8.0.0Compare Source
👓 Spec Compliance
babel-core💥 Breaking Change
babel-cli,babel-node,babel-plugin-proposal-decorators,babel-plugin-transform-classes,babel-plugin-transform-function-name,babel-plugin-transform-modules-commonjs,babel-plugin-transform-object-rest-spread,babel-plugin-transform-parameters,babel-plugin-transform-react-constant-elements,babel-plugin-transform-regenerator,babel-preset-env,babel-registermodules: auto(@nicolo-ribaudo)babel-plugin-transform-runtime,babel-runtime-corejs3,babel-runtime@babe/runtime-corejs3(@liuxingbaoyu)babel-parserlocations: "packed"(@liuxingbaoyu)🐛 Bug Fix
babel-generatorbabel-plugin-transform-modules-systemjs📝 Documentation
🏠 Internal
🏃♀️ Performance
babel-coredotansimha/graphql-code-generator (@graphql-codegen/typescript)
v6.1.0Compare Source
Minor Changes
959915fThanks @eddeee888! - dependencies updates:
graphql@^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0↗︎(from
^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0, inpeerDependencies)Patch Changes
[
959915f,959915f,959915f]:v6.0.2Compare Source
Patch Changes
55a4742Thanks @eddeee888! - dependencies updates:
@graphql-codegen/plugin-helpers@workspace:^↗︎(from
^7.0.0, independencies)@graphql-codegen/schema-ast@workspace:^↗︎(from
^6.0.0, independencies)@graphql-codegen/visitor-plugin-common@workspace:^↗︎(from
^7.0.1, independencies)[
55a4742,55a4742]: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]:dotansimha/graphql-code-generator (@graphql-codegen/typescript-operations)
v6.1.0Compare Source
Minor Changes
959915fThanks @eddeee888! - dependencies updates:
graphql@^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0↗︎(from
^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0,in
peerDependencies)Patch Changes
[
959915f,959915f,959915f]:v6.0.5Compare Source
Patch Changes
8a65a1bThanks @vkbansal-rubrik! - handles conditional spread of a
fragment whose top-level selections are fragment spreads or contain inline fragments
[
8a65a1b]:v6.0.4Compare Source
Patch Changes
16b9529Thanks @vinassefranche! - Fix Array used instead of
ReadonlyArray while immutableTypes config is true
v6.0.3Compare Source
Patch Changes
55a4742Thanks @eddeee888! - dependencies updates:
@graphql-codegen/plugin-helpers@workspace:^↗︎(from
^7.0.0, independencies)@graphql-codegen/schema-ast@workspace:^↗︎(from
^6.0.0, independencies)@graphql-codegen/visitor-plugin-common@workspace:^↗︎(from
^7.0.1, independencies)[
55a4742,55a4742]:v6.0.2Compare Source
Patch Changes
297c896Thanks @eddeee888! - Fix
typescript-operationsincosistentscalar overrides for native scalars
v6.0.1Compare Source
Patch Changes
#10781
5f035cbThanks @eddeee888! - Fix
constenum applyingtypesPrefixandtypesSuffixincorrectlyUpdated dependencies
[
5f035cb]: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]:microsoft/TypeScript (typescript)
v7.0.2Compare Source
qmhc/unplugin-dts (vite-plugin-dts)
v5.0.3Compare Source
v5.0.2Compare Source
v5.0.1Compare Source
v5.0.0Compare Source
Configuration
📅 Schedule: (in timezone Europe/Berlin)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.