Bump @apollo/client from 3.13.9 to 4.2.12

[dependabot]

Bumps @apollo/client from 3.13.9 to 4.2.12.

Release notes

Sourced from @​apollo/client's releases.

@​apollo/client@​4.2.12

Patch Changes

• #13400 56ca81b Thanks @​QiRaining! - Preserve multi-byte UTF-8 characters split across multipart response chunks.

@​apollo/client@​4.2.11

Patch Changes

• #13398 3dd3e9a Thanks @​phryneas! - Fix type signature of some DocumentationTypes to fix their display in our documentation.

• #13392 d4f0771 Thanks @​jerelmiller! - Add a development-only warning when a network result is written to the cache but reading the query back from the cache returns a partial result. This usually points at a merge or read function that did not repair missing fields in the cache, which prevents Apollo Client from applying the cache result to the data received by the network.

@​apollo/client@​4.2.10

Patch Changes

• #13385 bfb674e Thanks @​jerelmiller! - Fix accidental widening of the client.mutate return type when optimisticResponse was present.

• #13382 365373e Thanks @​jerelmiller! - Fix result types widened when a query's variables had constant types (e.g. TypedDocumentNode<Data, { type: "main" }>). This caused options such as returnPartialData or errorPolicy to be reported as their widened types (e.g. boolean, ErrorPolicy) instead of the value that was passed which returned the wrong data and dataState types.

• #13382 365373e Thanks @​jerelmiller! - Fix issue where unknown options were permitted by TypeScript when passed alongside a valid option to APIs with modern signatures.

• #13383 5840f50 Thanks @​jerelmiller! - Update the return type of refetch, fetchMore and useLazyQuery's execute function on the provided errorPolicy. Previously these APIs all used the default type which typed data as TData | undefined and error as ErrorLike | undefined.

@​apollo/client@​4.2.9

Patch Changes

• #13364 2f383e7 Thanks @​atharv-sys32! - Fix a bug where GraphQL variable default values were not applied during cache reads when variables with defaults were explicitly set to undefined. This caused @include/@skip directives to throw "Invalid variable referenced" errors when the variable was passed as undefined instead of being omitted entirely.

• #13367 2b39cc8 Thanks @​jerelmiller! - Fix an issue where some @export queries would not react to cache updates when the fields keyed by exported variables were updated.

@​apollo/client@​4.2.8

Patch Changes

• #13349 501a33b Thanks @​jerelmiller! - Prevent the setTimeout in connectToDevtools that shows the devtools suggestion from firing when the user agent does not match Chrome or Firefox. This check was previously done inside the setTimeout which meant the timer was scheduled for environments where we'd never show the message anyways. For test environments, this could cause flaky tests when that setTimeout outlived the tests and ran after any virtual DOM was torn down and removed.

@​apollo/client@​4.2.7

Patch Changes

• #13320 538c906 Thanks @​jerelmiller! - Cleanup some unused internals. Please file an issue if you notice anything change.

@​apollo/client@​4.2.6

Patch Changes

• #13315 a406cc9 Thanks @​fallintoplace! - Prevent relay multipart subscriptions from issuing a fetch request after serializing the request body fails.

• #13307 abd0781 Thanks @​wolfie! - Speed up cache writes by avoiding a full AST visit of every written field to detect @stream. The check now runs only when the result carries stream info, and only inspects the field node's own directives. As a result, fields that merely contain @stream on a nested field are no longer treated as streamed themselves and now overwrite existing lists like regular fields instead of merging chunk-wise.

@​apollo/client@​4.2.5

Patch Changes

... (truncated)

Changelog

Sourced from @​apollo/client's changelog.

4.2.12

Patch Changes

• #13400 56ca81b Thanks @​QiRaining! - Preserve multi-byte UTF-8 characters split across multipart response chunks.

4.2.11

Patch Changes

• #13398 3dd3e9a Thanks @​phryneas! - Fix type signature of some DocumentationTypes to fix their display in our documentation.

• #13392 d4f0771 Thanks @​jerelmiller! - Add a development-only warning when a network result is written to the cache but reading the query back from the cache returns a partial result. This usually points at a merge or read function that did not repair missing fields in the cache, which prevents Apollo Client from applying the cache result to the data received by the network.

4.2.10

Patch Changes

• #13385 bfb674e Thanks @​jerelmiller! - Fix accidental widening of the client.mutate return type when optimisticResponse was present.

• #13382 365373e Thanks @​jerelmiller! - Fix result types widened when a query's variables had constant types (e.g. TypedDocumentNode<Data, { type: "main" }>). This caused options such as returnPartialData or errorPolicy to be reported as their widened types (e.g. boolean, ErrorPolicy) instead of the value that was passed which returned the wrong data and dataState types.

• #13382 365373e Thanks @​jerelmiller! - Fix issue where unknown options were permitted by TypeScript when passed alongside a valid option to APIs with modern signatures.

• #13383 5840f50 Thanks @​jerelmiller! - Update the return type of refetch, fetchMore and useLazyQuery's execute function on the provided errorPolicy. Previously these APIs all used the default type which typed data as TData | undefined and error as ErrorLike | undefined.

4.2.9

Patch Changes

• #13364 2f383e7 Thanks @​atharv-sys32! - Fix a bug where GraphQL variable default values were not applied during cache reads when variables with defaults were explicitly set to undefined. This caused @include/@skip directives to throw "Invalid variable referenced" errors when the variable was passed as undefined instead of being omitted entirely.

• #13367 2b39cc8 Thanks @​jerelmiller! - Fix an issue where some @export queries would not react to cache updates when the fields keyed by exported variables were updated.

4.2.8

Patch Changes

• #13349 501a33b Thanks @​jerelmiller! - Prevent the setTimeout in connectToDevtools that shows the devtools suggestion from firing when the user agent does not match Chrome or Firefox. This check was previously done inside the setTimeout which meant the timer was scheduled for environments where we'd never show the message anyways. For test environments, this could cause flaky tests when that setTimeout outlived the tests and ran after any virtual DOM was torn down and removed.

4.2.7

Patch Changes

• #13320 538c906 Thanks @​jerelmiller! - Cleanup some unused internals. Please file an issue if you notice anything change.

4.2.6

Patch Changes

... (truncated)

Commits

• a4a170f Version Packages (#13411)
• 56ca81b Fix UTF-8 decoding across multipart chunks (#13400)
• b124349 Speed up CI (#13410)
• ba511be Version Packages (#13401)
• d4f0771 Warn when rereading a partial cache result after a write (#13392)
• 3dd3e9a Fix type signature of some DocumentationTypes to fix their display in our d...
• 4947447 Version Packages (#13389)
• bfb674e Fix client.mutate return type when optimisticResponse is provided (#13385)
• 5840f50 Update return types for refetch, fetchMore and useLazyQuery execute o...
• 365373e Fix widening of default options types when variables contain constant types (...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​apollo/client since your current version.