Skip to content

[pull] master from dotansimha:master #111

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.

Sign up for GitHub

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

Merged
pull merged 1 commit into from
Mar 24, 2026
Merged

[pull] master from dotansimha:master #111

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 18 additions & 2 deletions website/src/pages/docs/migration/operations-and-client-preset-from-5-0.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -386,14 +386,30 @@ The following utility types have been removed:
- `InputMaybe`: used to handle nullability types of Input. Input types are now inlined, so this type is no longer needed.
- `MakeOptional`, `MakeMaybe` and `MakeEmpty`: used to handle `preResolveTypes:false`. However, `preResolveTypes` has been removed, so these types are no longer needed.

### 11. Make `unknown` the default type for custom scalars instead of `any`
### 11. `unknown` is the default type for custom scalars instead of `any`

Previously, the default custom Scalars type was `any`, which bypassed typechecking.

Now, the default type is `unknown` to ensure data is handled carefully by users.

### 12. Make `string | number` the default type for the native `ID` scalar
### 12. `string | number` is the default type for the native `ID` scalar

Previously, one set of default Scalar types was shared between client and server plugins via the `typescript` plugin dependency. This meant it was not possible to set the default for client, as it would complicate the server config, and vice versa. See this [PR for more details](https://github.com/dotansimha/graphql-code-generator/pull/9497).

Now, the `typescript` plugin is no longer a dependency. So, we can set the default type as `string | number`, which is the correct type for client use cases. For more details on how Scalar coercion works here, please read [The Complete GraphQL Scalar Guide](https://the-guild.dev/graphql/hive/blog/the-complete-graphql-scalar-guide#scalar-value-coercion).

### 13. client-preset persisted document default hash algorithm is SHA256

Previously, the default hash algorithm for persisted documents was `sha1`.

Now, the default is `sha256`. When using `sha256`, the generated hash conforms to the format defined in the [GraphQL over HTTP spec for persisted document identifiers](https://github.com/graphql/graphql-over-http/blob/52d56fb36d51c17e08a920510a23bdc2f6a720be/spec/Appendix%20A%20--%20Persisted%20Documents.md#sha256-hex-document-identifier).

### 14. Core plugins have ESM dependencies

<Callout>This change mainly impacts plugin maintainers.</Callout>

Previously, core plugins were stuck on older dependency versions because ESM-only packages made integration and testing harder for maintainers.

Now, Node.js 20 support has been dropped, Node.js 22 can load ESM seamlessly at runtime, with no extra configuration. This allows core plugins to adopt dependencies that are ESM-only.

Plugin maintainers using [Jest](https://jestjs.io/) may still encounter issues. We recommend switching to [Vitest](https://vitest.dev/), which has native ESM support.
Loading