fix(deps): update minor and patch dependencies for gatsby-source-graphql

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@apollo/client (source)	^3.5.10 -> ^3.7.13
@graphql-tools/links	^8.2.14 -> ^8.3.36
@graphql-tools/utils	^8.6.9 -> ^8.13.1
@graphql-tools/wrap	^8.3.3 -> ^8.5.1
dataloader	^2.0.0 -> ^2.2.2
node-fetch	^2.6.7 -> ^2.6.9

---

Release Notes

apollographql/apollo-client

v3.7.13

Compare Source

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

Compare Source

Patch Changes

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

v3.7.11

Compare Source

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.

• #​10629 02605bb3c Thanks @​phryneas! - useQuery: delay unsubscribe to fix race conditions

v3.7.10

Compare Source

Patch Changes

• #​9438 52a9c8ea1 Thanks @​dciesielkiewicz! - Ensure the client option passed to useMutation's execute function is used when provided. Previously this option was ignored.

• #​9124 975b923c0 Thanks @​andrebrantom! - Make ApolloClient.writeQuery and ApolloClient.writeFragment behave more like cache.writeQuery and cache.writeFragment by returning the reference returned by the cache.

v3.7.9

Compare Source

Patch Changes

• #​10560 a561ecf43 Thanks @​benjamn! - Keep __typename fragment when it does not contain @client directive and strip out inline fragments which use a @client directive. Thanks @​Gazler and @​mtsmfm!

• #​10560 251a12806 Thanks @​benjamn! - Refactor removeDirectivesFromDocument to fix AST ordering sensitivities and avoid 1/3 AST traversals, potentially improving performance for large queries

v3.7.8

Compare Source

Patch Changes

• #​7555 45562d6fa Thanks @​TheCeloReis! - Adds TVariables generic to GraphQLRequest and MockedResponse interfaces.

• #​10526 1d13de4f1 Thanks @​benjamn! - Tolerate undefined concast.sources if complete called earlier than concast.start

• #​10497 8a883d8a1 Thanks @​nevir! - Update SingleExecutionResult and IncrementalPayload's data types such that they no longer include undefined, which was not a valid runtime value, to fix errors when TypeScript's exactOptionalPropertyTypes is enabled.

v3.7.7

Compare Source

Patch Changes

• #​10502 315faf9ca Thanks @​jerelmiller! - Log a warning to the console when a mock passed to MockedProvider or MockLink cannot be matched to a query during a test. This makes it easier to debug user errors in the mock setup, such as typos, especially if the query under test is using an errorPolicy set to ignore, which makes it difficult to know that a match did not occur.

• #​10499 9e54f5dfa Thanks @​phryneas! - Allow the execution function returned by useLazyQuery to change the query.

• #​10362 14a56b105 Thanks @​mccraveiro! - Fix error when server returns an error and we are also querying for a local field

v3.7.6

Compare Source

Patch Changes

• #​10470 47435e879 Thanks @​alessbell! - Bumps TypeScript to 4.9.4 (previously 4.7.4) and updates types to account for changes in TypeScript 4.8 by propagating contstraints on generic types. Technically this makes some types stricter as attempting to pass null|undefined into certain functions is now disallowed by TypeScript, but these were never expected runtime values in the first place.

• #​10408 55ffafc58 Thanks @​zlrlo! - fix: modify BatchHttpLink to have a separate timer for each different batch key

• #​9573 4a4f48dda Thanks @​vladar! - Improve performance of local resolvers by only executing selection sets that contain an @client directive. Previously, local resolvers were executed even when the field did not contain @client. While the result was properly discarded, the unncessary work could negatively affect query performance, sometimes signficantly.

v3.7.5

Compare Source

Patch Changes

• #​10458 b5ccef229 Thanks @​lennyburdette! - Passes getServerSnapshot to useSyncExternalStore so that it doesn't trigger a Missing getServerSnapshot error when using useFragment_experimental on the server.

• #​10471 895ddcb54 Thanks @​alessbell! - More robust type definition for headers property passed to createHttpLink

• #​10321 bbaa3ef2d Thanks @​alessbell! - Refetch should not return partial data with errorPolicy: none and notifyOnNetworkStatusChange: true.

• #​10402 0b07aa955 Thanks @​Hugodby! - Improve context types

• #​10469 328c58f90 Thanks @​jerelmiller! - Add generic type defaults when using useFragment to allow passing TData directly to the function without needing to specify TVars.

v3.7.4

Compare Source

Patch Changes

• #​10427 28d909cff Thanks @​jerelmiller! - Ensure in-flight promises executed by useLazyQuery are rejected when useLazyQuery unmounts.

• #​10383 5c5ca9b01 Thanks @​jerelmiller! - Ensure the onError callback is called when the errorPolicy is set to "all" and partial data is returned.

• #​10425 86e35a6d2 Thanks @​jerelmiller! - Prefer the onError and onCompleted callback functions passed to the execute function returned from useMutation instead of calling both callback handlers.

v3.7.3

Compare Source

Patch Changes

• #​10334 7d923939d Thanks @​jerelmiller! - Better handle deferred queries that have cached or partial cached data for them

• #​10368 46b58e976 Thanks @​alessbell! - Fix: unblocks support for defer in mutations

  If the @defer directive is present in the document passed to mutate, the Promise will resolve with the final merged data after the last multipart chunk has arrived in the response.

v3.7.2

Compare Source

Patch Changes

• Only show dev tools suggestion in the console when connectToDevTools is true.
  
  @​chris110408 in #​10258

• Pass TCache generic to MutationHookOptions for better type support in useMutation.
  
  @​igrlk in #​10223

• Add name property to ApolloError to ensure better type safety and help error reporting tools better identify the error.
  
  @​aaronadamsCA in #​9323

• Export a ModifierDetails type for the details parameter of a Modifier function.
  
  @​KeithGillette in #​7133

• Revert use of cloneDeep to clone options when fetching queries.
  
  @​MrDoomBringer in #​10215

v3.7.1

Compare Source

Patch Changes

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

v3.7.0

Compare Source

Minor Changes

• Implement preview support for the @defer directive.
  
  @​alessbell and @​benjamn in #​10018

• Implement useFragment_experimental hook, which represents a lightweight live binding into the ApolloCache, and never triggers network requests of its own.
  
  @​benjamn in #​8782

• Allow registering named fragments with InMemoryCache to support using ...NamedFragment in queries without redeclaring NamedFragment repeatedly in every query that uses it.
  
  @​benjamn in #​9764

• Support onError callback for useSubscription hook.
  
  @​jeroenvisser101 in #​9495

• Implement preserveHeaderCase option for http context object, enabling preserved header capitalization for non-http-spec-compliant servers.
  
  @​mrdoombringer in #​9891

Patch Changes

• Delay calling onCompleted and onError callbacks passed to useQuery using Promise.resolve().then(() => ...) to fix issue #​9794.
  
  @​dylanwulf in #​9823

• Replace concast.cleanup method with simpler concast.beforeNext API, which promises to call the given callback function just before the next result/error is delivered. In addition, concast.removeObserver no longer takes a quietly?: boolean parameter, since that parameter was partly responsible for cleanup callbacks sometimes not getting called.
  
  @​benjamn in #​9718

• Allow preserving header name capitalization when creating an HttpLink with createHttpLink({ uri, preserveHeaderCase: true }). Otherwise, header names are converted to lowercase to prevent case-sensitivity bugs.
  
  @​MrDoomBringer in #​9891

• Make queries with a pollInterval respect the no-cache fetch policy, instead of writing polled results into the cache.
  
  @​MrDoomBringer in #​10020

• Deprecate the onSubscriptionData callback in favor of a new onData callback for the useSubscription hook. Deprecate the onSubscriptionComplete callback in favor of a new onComplete callback for the useSubscription hook.
  
  @​jerelmiller in #​10134

Potentially disruptive

• The optional subscribeAndCount testing utility exported from @apollo/client/testing/core now takes a single generic TResult type parameter, instead of TData. This type will typically be inferred from the observable argument type, but if you have any explicit calls to subscribeAndCount<TData>(...) in your own codebase, you may need to adjust those calls accordingly.
  
  @​benjamn in #​9718

v3.6.10

Compare Source

Improvements

• The client options (variables, context, etc.) used for mutation calls are now available as the second argument to the onCompleted and onError callback functions.
  
  @​MrDoomBringer in #​10052

v3.6.9

Compare Source

Bug Fixes

• Leave fetchPolicy unchanged when skip: true (or in standby) and nextFetchPolicy is available, even if variables change.
  
  @​benjamn in #​9823

v3.6.8

Compare Source

Bug Fixes

• Fix incorrect variables passed in FieldFunctionOptions for nested readField calls in read and merge functions.
  
  @​stardustxx in #​9808

• Improve repository build scripts to work better on Windows.
  
  @​dylanwulf in #​9805

• Ensure useQuery(query, { skip: true }).called === false rather than always returning called as true.
  
  @​KucharskiPiotr in #​9798

• Allow abandoned reobserve requests to unsubscribe from their underlying Observable.
  
  @​javier-garcia-meteologica in #​9791

v3.6.7

Compare Source

Bug Fixes

• Fix regression (introduced in v3.6.0) that caused BatchHttpLink to discard pending batched queries on early completion of the underlying Observable.
  
  @​benjamn in #​9793

v3.6.6

Compare Source

Bug Fixes

• Allow useLazyQuery(query, { defaultOptions }) to benefit from defaultOptions.variables and client.defaultOptions.watchQuery.variables merging.
  
  @​benjamn in #​9762

v3.6.5

Compare Source

Bug Fixes

• Restore pre-v3.6 variables replacement behavior of ObservableQuery#reobserve method, fixing a regression that prevented removal of variables.
  
  @​benjamn in #​9741

• Preserve previousData even when different query or client provided to useQuery, instead of resetting previousData to undefined in those cases, matching behavior prior to v3.6.0.
  
  @​benjamn in #​9734

• Fix bug where onCompleted() and onError() are stale for useMutation().
  
  @​charle692 in #​9740

• Limit scope of DeepMerger object reuse, and avoid using Object.isFrozen, which can introduce differences between development and production if objects that were frozen using Object.freeze in development are left unfrozen in production.
  
  @​benjamn in #​9742

• Properly merge variables from original useLazyQuery(query, { variables }) with variables passed to execution function.
  
  @​benjamn in #​9758

v3.6.4

Compare Source

Bug Fixes

• Guarantee Concast cleanup without Observable cancelled prematurely rejection, potentially solving long-standing issues involving that error.
  
  @​benjamn in #​9701

• Ensure useSubscription subscriptions are properly restarted after unmounting/remounting by React 18 in <StrictMode>.
  
  @​kazekyo in #​9707

Improvements

• Internalize useSyncExternalStore shim, for more control than use-sync-external-store provides, fixing some React Native issues.
  
  @​benjamn in #​9675 and #​9709

• Provide @apollo/client/**/*.cjs.native.js versions of every @apollo/client/**/*.cjs bundle (including dependencies ts-invariant and zen-observable-ts) to help React Native's Metro bundler automatically resolve CommonJS entry point modules. These changes should render unnecessary the advice we gave in the v3.5.4 section below about metro.config.js.
  
  @​benjamn in #​9716

• Handle falsy incoming data more gracefully in offetLimitPagination().merge function.
  
  @​shobhitsharma in #​9705

v3.6.3

Compare Source

Bug Fixes

• Simplify useQuery(query, { defaultOptions }) default options processing in order to fix bug where skip: true queries failed to execute upon switching to skip: false.
  
  @​benjamn in #​9665

• Add tests of skipping/unskipping and useLazyQuery with defaultOptions, and fix a bug causing duplicate requests.
  
  @​benjamn in #​9666

• Update ts-invariant to version 0.10.2 to fix source map warnings.
  
  @​benjamn in #​9672

• Test that useQuery queries with skip: true do not stall server-side rendering.
  
  @​nathanmarks and @​benjamn in #​9677

• Prevent useLazyQuery from making duplicate requests when its execution function is first called, and stop rejecting the Promise it returns when result.error is defined.
  
  @​benjamn in #​9684

• Fix issue with useQuery returning loading: true state during server-side rendering with skip: true.
  
  @​nathanmarks in #​9679

v3.6.2

Compare Source

Bug Fixes

• Pass getServerSnapshot function to useSyncExternalStore in addition to getSnapshot, though the two functions behave identically. This change should fix/unbreak React 18 server rendering.
  
  @​hungphongbk in #​9652

Improvements

• Consider networkError.result.errors in addition to result.errors in PersistedQueryLink.
  
  @​redaid113 and @​benjamn in #​9410

v3.6.1

Compare Source

Improvements

• The client options (variables, context, etc.) used for mutation calls are now available as the second argument to the onCompleted and onError callback functions.
  
  @​MrDoomBringer in #​10052

v3.6.0

Compare Source

Potentially disruptive changes

• Calling fetchMore for queries using the cache-and-network or network-only fetch policies will no longer trigger additional network requests when cache results are complete. Instead, those complete cache results will be delivered as if using the cache-first fetch policy.
  
  @​benjamn in #​9504

• Reimplement useQuery and useLazyQuery to use the proposed useSyncExternalStore API from React 18.
  
  @​brainkim and @​benjamn in #​8785 and #​9596

• Fixed bug where the useLazyQuery execution function would always use the refetch method of ObservableQuery, instead of properly reapplying the current fetchPolicy using the reobserve method.
  
  @​benjamn in #​9564

  Since this reobserve method is useful and used internally, we have now exposed it as use[Lazy]Query(...).reobserve (which optionally takes a Partial<WatchQueryOptions> of new options), to supplement the existing refetch method. Note that reobserve permanently updates the variables and other options of the ObservableQuery, unlike refetch({ ...variables }), which does not save those variables.

• The internal use of options.fetchBlockingPromise by useQuery and useLazyQuery may slightly delay the delivery of network results, compared to previous versions of Apollo Client. Since network results are already delivered asynchronously, these timing differences should not be disruptive in most cases. Nevertheless, please open an issue if the timing differences are a problem for you (and you have no easy workaround).
  
  @​benjamn in #​9599

React 18

In both its peerDependencies and its internal implementation, Apollo Client v3.6 should no longer prevent you from updating to React 18 in your applications.

Internally, we have refactored useQuery and useLazyQuery to be implemented in terms of React's new (shimmable) useSyncExternalStore hook, demonstrating Apollo Client can serve as an external store with a referentially stable, synchronous API, as needed by React.

As part of this refactoring, we also improved the behavior of useQuery and useLazyQuery when used in <React.StrictMode>, which double-renders components in development. While this double-rendering always results in calling useQuery twice, forcing Apollo Client to create and then discard an unnecessary ObservableQuery object, we now have multiple defenses in place against executing any network queries for the unused ObservableQuery objects.

In upcoming v3.6.x and v3.7 (beta) releases, we will be completely overhauling our server-side rendering utilities (getDataFromTree et al.), and introducing suspenseful versions of our hooks, to take full advantage of the new patterns React 18+ enables for data management libraries like Apollo Client.

Improvements

• Allow BatchLink to cancel queued and in-flight operations.
  
  @​PowerKiKi and @​benjamn in #​9248

• Add GraphQLWsLink in @apollo/client/link/subscriptions. This link is similar to the existing WebSocketLink in @apollo/client/link/ws, but uses the newer graphql-ws package and protocol instead of the older subscriptions-transport-ws implementation. This functionality was technically first released in @apollo/[email protected], but semantically belongs in the 3.6.0 minor version.
  @​glasser in #​9369

• Allow passing defaultOptions to useQuery to avoid clobbering/resetting existing options when useQuery is called repeatedly.
  
  @​benjamn in #​9563, superseding #​9223

• Provide additional context to nextFetchPolicy functions to assist with fetchPolicy transitions. More details can be found in the nextFetchPolicy documentation.
  
  @​benjamn in #​9222

• Remove nagging deprecation warning about passing an options.updateQuery function to fetchMore.
  
  @​benjamn in #​9504

• Let addTypenameToDocument take any ASTNode (including DocumentNode, as before).
  
  @​benjamn in #​9595

• Set useMutation internal isMounted variable to true again when component remounted.
  
  @​devpeerapong in #​9561

ardatan/graphql-tools (@​graphql-tools/links)

v8.3.36

Compare Source

Patch Changes

• #​5202 05c97eb8 Thanks @​ardatan! - dependencies updates:
  • Updated dependency @apollo/client@^3 ↗︎ (from ~3.2.5 || ~3.3.0 || ~3.4.0 || ~3.5.0 || ~3.6.0 || ~3.7.0, in peerDependencies)
• Updated dependencies []:
  • @​graphql-tools/delegate@​9.0.33

v8.3.35

Compare Source

Patch Changes

• 1c95368a Thanks @​ardatan! - Use ranged versions for dependencies

• Updated dependencies []:

  • @​graphql-tools/delegate@​9.0.31

v8.3.34

Compare Source

Patch Changes

• Updated dependencies []:
  • @​graphql-tools/delegate@​9.0.30

v8.3.33

Compare Source

Patch Changes

• Updated dependencies [f26392a6]:
  • @​graphql-tools/delegate@​9.0.29

v8.3.32

Compare Source

Patch Changes

• Updated dependencies [492220cb]:
  • @​graphql-tools/delegate@​9.0.28

v8.3.31

Compare Source

Patch Changes

• Updated dependencies [30bd4d0c]:
  • @​graphql-tools/delegate@​9.0.27

v8.3.30

Compare Source

Patch Changes

• Updated dependencies [b09ea282, b5c8f640]:
  • @​graphql-tools/delegate@​9.0.26
  • @​graphql-tools/utils@​9.2.1

v8.3.29

Compare Source

Patch Changes

• Updated dependencies [a94217e9, 62d074be]:
  • @​graphql-tools/utils@​9.2.0
  • @​graphql-tools/delegate@​9.0.25

v8.3.28

Compare Source

Patch Changes

• Updated dependencies [772b948a]:
  • @​graphql-tools/delegate@​9.0.24

v8.3.27

Compare Source

Patch Changes

• Updated dependencies []:
  • @​graphql-tools/delegate@​9.0.23

v8.3.26

Compare Source

Patch Changes

• Updated dependencies [a4d36fcc, e3ec35ed]:
  • @​graphql-tools/delegate@​9.0.22
  • @​graphql-tools/utils@​9.1.4

v8.3.25

Compare Source

Patch Changes

• Updated dependencies [13177794]:
  • @​graphql-tools/delegate@​9.0.21

v8.3.24

Compare Source

Patch Changes

• Updated dependencies [eb6cd8b6, eb6cd8b6]:
  • @​graphql-tools/delegate@​9.0.20

v8.3.23

Compare Source

Patch Changes

• Updated dependencies [904fe770, 904fe770]:
  • @​graphql-tools/utils@​9.1.3
  • @​graphql-tools/delegate@​9.0.19

v8.3.22

Compare Source

Patch Changes

• Updated dependencies [13c24883, b5e6459f]:
  • @​graphql-tools/delegate@​9.0.18
  • @​graphql-tools/utils@​9.1.2

v8.3.21

Compare Source

Patch Changes

• Updated dependencies [7411a5e7]:
  • @​graphql-tools/utils@​9.1.1
  • @​graphql-tools/delegate@​9.0.17

v8.3.20

Compare Source

Patch Changes

• Updated dependencies []:
  • @​graphql-tools/delegate@​9.0.16

v8.3.19

Compare Source

Patch Changes

• Updated dependencies [c0639dd0]:
  • @​graphql-tools/utils@​9.1.0
  • @​graphql-tools/delegate@​9.0.15

v8.3.18

Compare Source

Patch Changes

• Updated dependencies [d83b1960]:
  • @​graphql-tools/utils@​9.0.1
  • @​graphql-tools/delegate@​9.0.14

v8.3.17

Compare Source

Patch Changes

• Updated dependencies []:
  • @​graphql-tools/delegate@​9.0.13

v8.3.16

Compare Source

Patch Changes

• Updated dependencies []:
  • @​graphql-tools/delegate@​9.0.12

v8.3.15

Compare Source

Patch Changes

• Updated dependencies [80836fa7, 8f6d3efc, 80836fa7, 80836fa7, 80836fa7]:
  • @​graphql-tools/utils@​9.0.0
  • @​graphql-tools/delegate@​9.0.11

v8.3.14

Compare Source

Patch Changes

• Updated dependencies [f7daf777]:
  • @​graphql-tools/utils@​8.13.1
  • @​graphql-tools/delegate@​9.0.10

v8.3.13

Compare Source

Patch Changes

• Updated dependencies [df5848b8, df5848b8, df5848b8, df5848b8]:
  • @​graphql-tools/delegate@​9.0.9
  • @​graphql-tools/utils@​8.13.0

v8.3.12

Compare Source

Patch Changes

• [#​4701](https://togith

---

Configuration

📅 Schedule: Branch creation - "before 7am on the first day of the month" in timezone GMT, Automerge - At any time (no schedule defined).

🚦 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.