chore(deps): bump @apollo/client from 3.7.10 to 3.7.15

[dependabot]

Bumps @apollo/client from 3.7.10 to 3.7.15.

Release notes

Sourced from @​apollo/client's releases.

v3.7.15

Patch Changes

• #10891 ab42a5c08 Thanks @​laverdet! - Fixes a bug in how multipart responses are read when using @defer. When reading a multipart body, HttpLink no longer attempts to parse the boundary (e.g. "---" or other boundary string) within the response data itself, only when reading the beginning of each mulitpart chunked message.

• #10789 23a4e1578 Thanks @​phryneas! - Fix a bug where other fields could be aliased to __typename or id, in which case an incoming result would be merged into the wrong cache entry.

v3.7.14

Patch Changes

• #10764 1b0a61fe5 Thanks @​phryneas! - Deprecate useFragment returnPartialData option

• #10810 a6252774f Thanks @​dleavitt! - Fix type signature of ServerError.

  In <3.7 HttpLink and BatchHttpLink would return a ServerError.message of e.g. "Unexpected token 'E', \"Error! Foo bar\" is not valid JSON" and a ServerError.result of undefined in the case where a server returned a >= 300 response code with a response body containing a string that could not be parsed as JSON.

  In >=3.7, message became e.g. Response not successful: Received status code 302 and result became the string from the response body, however the type in ServerError.result was not updated to include the string type, which is now properly reflected.

v3.7.13

Patch Changes

• #10805 a5503666c Thanks @​phryneas! - Fix a potential memory leak in SSR scenarios when many persistedQuery instances were created over time.

• #10718 577c68bdd Thanks @​Hsifnus! - Delay Concast subscription teardown slightly in useSubscription to prevent unexpected Concast teardown when one useSubscription hook tears down its in-flight Concast subscription immediately followed by another useSubscription hook reusing and subscribing to that same Concast

v3.7.12

Patch Changes

• #10735 895bcdcff Thanks @​alessbell! - If a multipart chunk contains only hasNext: false, immediately complete the observable.

v3.7.11

Patch Changes

• #10586 4175af594 Thanks @​alessbell! - Improve WebSocket error handling for generic Event received on error. For more information see https://developer.mozilla.org/en-US/docs/Web/API/WebSocket/error_event.

• #10411 152baac34 Thanks @​lovasoa! - Simplify error message generation and make 'undefined' an impossible message string.

• #10592 cdb98ae08 Thanks @​alessbell! - Adds support for multipart subscriptions in HttpLink.

• #10698 38508a251 Thanks @​jerelmiller! - Changes the behavior of useLazyQuery introduced in #10427 where unmounting a component before a query was resolved would reject the promise with an abort error. Instead, the promise will now resolve naturally with the result from the request.

  Other notable fixes:

  • Kicking off multiple requests in parallel with the execution function will now ensure each returned promise is resolved with the data from its request. Previously, each promise was resolved with data from the last execution.
  • Re-rendering useLazyQuery with a different query document will now ensure the execution function uses the updated query document. Previously, only the query document rendered the first time would be used for the request.

• #10660 364bee98f Thanks @​alessbell! - Upgrades TypeScript to v5. This change is fully backward-compatible and transparent to users.

• #10597 8fb9d190d Thanks @​phryneas! - Fix a bug where an incoming cache update could prevent future updates from the active link.

... (truncated)

Changelog

Sourced from @​apollo/client's changelog.

3.7.15

Patch Changes

• #10891 ab42a5c08 Thanks @​laverdet! - Fixes a bug in how multipart responses are read when using @defer. When reading a multipart body, HttpLink no longer attempts to parse the boundary (e.g. "---" or other boundary string) within the response data itself, only when reading the beginning of each mulitpart chunked message.

• #10789 23a4e1578 Thanks @​phryneas! - Fix a bug where other fields could be aliased to __typename or id, in which case an incoming result would be merged into the wrong cache entry.

3.7.14

Patch Changes

• #10764 1b0a61fe5 Thanks @​phryneas! - Deprecate useFragment returnPartialData option

• #10810 a6252774f Thanks @​dleavitt! - Fix type signature of ServerError.

  In = 300 response code with a response body containing a string that could not be parsed as JSON.

  In >=3.7, message became e.g. Response not successful: Received status code 302 and result became the string from the response body, however the type in ServerError.result was not updated to include the string type, which is now properly reflected.

3.7.13

Patch Changes

• #10805 a5503666c Thanks @​phryneas! - Fix a potential memory leak in SSR scenarios when many persistedQuery instances were created over time.

• #10718 577c68bdd Thanks @​Hsifnus! - Delay Concast subscription teardown slightly in useSubscription to prevent unexpected Concast teardown when one useSubscription hook tears down its in-flight Concast subscription immediately followed by another useSubscription hook reusing and subscribing to that same Concast

3.7.12

Patch Changes

• #10735 895bcdcff Thanks @​alessbell! - If a multipart chunk contains only hasNext: false, immediately complete the observable.

3.7.11

Patch Changes

• #10586 4175af594 Thanks @​alessbell! - Improve WebSocket error handling for generic Event received on error. For more information see https://developer.mozilla.org/en-US/docs/Web/API/WebSocket/error_event.

• #10411 152baac34 Thanks @​lovasoa! - Simplify error message generation and make 'undefined' an impossible message string.

• #10592 cdb98ae08 Thanks @​alessbell! - Adds support for multipart subscriptions in HttpLink.

• #10698 38508a251 Thanks @​jerelmiller! - Changes the behavior of useLazyQuery introduced in #10427 where unmounting a component before a query was resolved would reject the promise with an abort error. Instead, the promise will now resolve naturally with the result from the request.

  Other notable fixes:

  • Kicking off multiple requests in parallel with the execution function will now ensure each returned promise is resolved with the data from its request. Previously, each promise was resolved with data from the last execution.
  • Re-rendering useLazyQuery with a different query document will now ensure the execution function uses the updated query document. Previously, only the query document rendered the first time would be used for the request.

... (truncated)

Commits

• 4d19216 Version Packages (#10851)
• 7fd00b2 Update docs on @​defer directive usage with GraphQL Code Generator (#10910)
• 2ca595f chore(deps): update dependency @​types/node to v20.2.3 (#10904)
• a92eed9 chore(deps): update dependency @​typescript-eslint/parser to v5.59.7 (#10899)
• 1d070f8 chore(deps): update dependency terser to v5.17.4 (#10902)
• dee6dd7 chore(deps): update dependency rimraf to v5.0.1 (#10901)
• 2bf0292 chore(deps): update dependency @​types/node-fetch to v2.6.4 (#10897)
• 1c6c304 chore(deps): update slackapi/slack-github-action action to v1.24.0 (#10906)
• cb7fcb0 chore(deps): update dependency eslint to v8.41.0 (#10905)
• a96d385 chore(deps): update dependency graphql-ws to v5.13.1 (#10900)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)