chore(deps): pin dependencies

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Type	Update	Change	Age	Adoption	Passing	Confidence
@0no-co/graphqlsp	devDependencies	pin	^1.15.1 → 1.15.2
@apollo/client (source)	devDependencies	minor	4.0.11 → 4.1.3
@apollo/client (source)	devDependencies	minor	3.11.10 → 3.14.0
@apollo/client-3 (source)	devDependencies	minor	3.13.0 → 3.14.0
@apollo/datasource-rest	devDependencies	pin	^6.0.0 → 6.0.0
@apollo/server (source)	devDependencies	pin	^4.3.0 → 4.9.3
@changesets/cli (source)	devDependencies	minor	2.27.12 → 2.29.8
@eslint/js (source)	devDependencies	pin	^9.21.0 → 9.21.0
@graphql-codegen/fragment-matcher (source)	devDependencies	pin	^5.1.0 → 5.1.0
@graphql-codegen/typescript (source)	devDependencies	minor	4.0.9 → 4.1.6
@graphql-codegen/typescript-operations (source)	devDependencies	minor	4.2.3 → 4.6.1
@graphql-codegen/typescript-resolvers (source)	devDependencies	minor	4.1.0 → 4.5.2
@graphql-tools/mock (source)	devDependencies	minor	9.0.25 → 9.1.5
@parcel/watcher	devDependencies	minor	2.4.1 → 2.5.6
@testing-library/dom	devDependencies	pin	^10.4.1 → 10.4.1
@testing-library/jest-dom	devDependencies	pin	^6.0.0 → 6.1.2
@testing-library/react	devDependencies	pin	^16.0.0 → 16.0.0
@testing-library/user-event	devDependencies	pin	^14.5.1 → 14.5.2
@types/chrome (source)	devDependencies	minor	0.0.326 → 0.1.36
@​types/classnames	devDependencies	pin	^2.2.10 → 2.2.10
@types/jest (source)	devDependencies	pin	^29.5.0 → 29.5.14
@types/node (source)	devDependencies	pin	^22.0.0 → 22.0.0
@types/node (source)	devDependencies	minor	20.14.10 → 20.19.30
@types/react (source)	devDependencies	pin	^18.3.23 → 18.3.23
@types/react-dom (source)	devDependencies	pin	^18.3.7 → 18.3.7
@typescript-eslint/eslint-plugin (source)	devDependencies	minor	7.14.1 → 7.18.0
@typescript-eslint/parser (source)	devDependencies	minor	7.14.1 → 7.18.0
@vitejs/plugin-react (source)	devDependencies	pin	^4.5.2 → 4.5.2
classnames	devDependencies	pin	^2.2.6 → 2.2.6
eslint-plugin-jest-dom	devDependencies	minor	5.4.0 → 5.5.0
eslint-plugin-react	devDependencies	minor	7.34.3 → 7.37.5
eslint-plugin-testing-library	devDependencies	minor	6.2.2 → 6.5.0
graphql	devDependencies	pin	^16.6.0 → 16.8.1
graphql	devDependencies	pin	^16.0.0 → 16.8.1
graphql	devDependencies	minor	16.9.0 → 16.12.0
jest (source)	devDependencies	minor	30.0.5 → 30.2.0
lowdb	devDependencies	pin	^1.0.0 → 1.0.0
pkg-pr-new (source)	devDependencies	pin	^0.0.62 → 0.0.62
postcss (source)	devDependencies	minor	8.4.49 → 8.5.6
postcss-loader	devDependencies	minor	8.1.1 → 8.2.0
react (source)	devDependencies	pin	^18.2.0 → 18.2.0
react-dom (source)	devDependencies	pin	^18.2.0 → 18.2.0
react-router-dom (source)	devDependencies	pin	^6.0.0 → 6.11.2
rxjs (source)	devDependencies	pin	^7.8.2 → 7.8.2
tsx (source)	devDependencies	minor	4.11.0 → 4.21.0
typescript (source)	devDependencies	minor	5.5.4 → 5.9.3
typescript (source)	devDependencies	pin	^5.8.3 → 5.8.3
typescript (source)	devDependencies	minor	5.4.5 → 5.9.3
typescript-eslint (source)	devDependencies	minor	7.14.1 → 7.18.0
vite (source)	devDependencies	pin	^6.3.5 → 6.4.1
web-ext-plugin	devDependencies	minor	2.11.0 → 2.12.0
webpack	devDependencies	minor	5.101.3 → 5.104.1
ws	devDependencies	pin	^8.18.0 → 8.18.0
zone.js (source, changelog)	devDependencies	minor	0.14.7 → 0.16.0

Add the preset :preserveSemverRanges to your config if you don't want to pin your dependencies.

---

Release Notes

apollographql/apollo-client (@​apollo/client)

v4.1.3

Compare Source

Patch Changes

• #​13111 bf46fe0 Thanks @​RogerHYang! - Fix createFetchMultipartSubscription to support cancellation via AbortController

  Previously, calling dispose() or unsubscribe() on a subscription created by createFetchMultipartSubscription had no effect - the underlying fetch request would continue running until completion. This was because no AbortController was created or passed to fetch(), and no cleanup function was returned from the Observable.

v4.1.2

Compare Source

Patch Changes

• #​13105 8b62263 Thanks @​phryneas! - ssrMode, ssrForceFetchDelay or prioritizeCacheValues should not override fetchPolicy: 'cache-only', fetchPolicy: 'no-cache', fetchPolicy: 'standby', skip: true, or skipToken when reading the initial value of an ObservableQuery.

• #​13105 8b62263 Thanks @​phryneas! - Fix skipToken in useQuery with prerenderStatic and related SSR functions.

• #​13105 8b62263 Thanks @​phryneas! - Avoid fetches with fetchPolicy: no-cache in useQuery with prerenderStatic and related SSR functions.

v4.1.1

Compare Source

Patch Changes

• #​13103 dee7dcf Thanks @​jerelmiller! - Ensure @client fields that are children of aliased server fields are resolved correctly.

v4.1.0

Compare Source

Minor Changes

• #​13043 65e66ca Thanks @​jerelmiller! - Support headers transport for enhanced client awareness.

• #​12927 785e223 Thanks @​jerelmiller! - You can now provide a callback function as the context option on the mutate function returned by useMutation. The callback function is called with the value of the context option provided to the useMutation hook. This is useful if you'd like to merge the context object provided to the useMutation hook with a value provided to the mutate function.

  function MyComponent() {
    const [mutate, result] = useMutation(MUTATION, {
      context: { foo: true },
    });
  
    async function runMutation() {
      await mutate({
        // sends context as { foo: true, bar: true }
        context: (hookContext) => ({ ...hookContext, bar: true }),
      });
    }
  
    // ...
  }

• #​12923 94ea3e3 Thanks @​jerelmiller! - Fix an issue where deferred payloads that returned arrays with fewer items than the original cached array would retain items from the cached array. This change includes @stream arrays where stream arrays replace the cached arrays.

• #​12927 96b531f Thanks @​jerelmiller! - Don't set the fallback value of a @client field to null when a read function is defined. Instead the read function will be called with an existing value of undefined to allow default arguments to be used to set the returned value.

  When a read function is not defined nor is there a defined resolver for the field, warn and set the value to null only in that instance.

• #​12927 45ebb52 Thanks @​jerelmiller! - Add support for from: null in client.watchFragment and cache.watchFragment. When from is null, the emitted result is:

  {
    data: null,
    dataState: "complete",
    complete: true,
  }

• #​12926 2b7f2c1 Thanks @​jerelmiller! - Support the newer incremental delivery format for the @defer directive implemented in graphql@17.0.0-alpha.9. Import the GraphQL17Alpha9Handler to use the newer incremental delivery format with @defer.

  import { GraphQL17Alpha9Handler } from "@​apollo/client/incremental";
  
  const client = new ApolloClient({
    // ...
    incrementalHandler: new GraphQL17Alpha9Handler(),
  });

  [!NOTE]
  In order to use the GraphQL17Alpha9Handler, the GraphQL server MUST implement the newer incremental delivery format. You may see errors or unusual behavior if you use the wrong handler. If you are using Apollo Router, continue to use the Defer20220824Handler because Apollo Router does not yet support the newer incremental delivery format.

• #​12927 45ebb52 Thanks @​jerelmiller! - Add support for arrays with useFragment, useSuspenseFragment, and client.watchFragment. This allows the ability to use a fragment to watch multiple entities in the cache. Passing an array to from will return data as an array where each array index corresponds to the index in the from array.

  function MyComponent() {
    const result = useFragment({
      fragment,
      from: [item1, item2, item3],
    });
  
    // `data` is an array with 3 items
    console.log(result); // { data: [{...}, {...}, {...}], dataState: "complete", complete: true }
  }

• #​12927 45ebb52 Thanks @​jerelmiller! - Add a getCurrentResult function to the observable returned by client.watchFragment and cache.watchFragment that returns the current value for the watched fragment.

  const observable = client.watchFragment({
    fragment,
    from: { __typename: "Item", id: 1 },
  });
  
  console.log(observable.getCurrentResult());
  // {
  //   data: {...},
  //   dataState: "complete",
  //   complete: true,
  // }

• #​13038 109efe7 Thanks @​jerelmiller! - Add the from option to readFragment, watchFragment, and updateFragment.

• #​12918 2e224b9 Thanks @​jerelmiller! - Add support for the @stream directive on both the Defer20220824Handler and the GraphQL17Alpha2Handler.

  [!NOTE]
  The implementations of @stream differ in the delivery of incremental results between the different GraphQL spec versions. If you upgrading from the older format to the newer format, expect the timing of some incremental results to change.

• #​13056 b224efc Thanks @​jerelmiller! - InMemoryCache no longer filters out explicitly returned undefined items from read functions for array fields. This now makes it possible to create read functions on array fields that return partial data and trigger a fetch for the full list.

• #​13058 121a2cb Thanks @​jerelmiller! - Add an extensions option to cache.write, cache.writeQuery, and client.writeQuery. This makes extensions available in cache merge functions which can be accessed with the other merge function options.

  As a result of this change, any extensions returned in GraphQL operations are now available in merge in the cache writes for these operations.

• #​12927 96b531f Thanks @​jerelmiller! - Add an abstract resolvesClientField function to ApolloCache that can be used by caches to tell LocalState if it can resolve a @client field when a local resolver is not defined.

  LocalState will emit a warning and set a fallback value of null when no local resolver is defined and resolvesClientField returns false, or isn't defined. Returning true from resolvesClientField signals that a mechanism in the cache will set the field value. In this case, LocalState won't set the field value.

• #​13078 bf1e0dc Thanks @​phryneas! - Use the default stream merge function for @stream fields only if stream info is present. This change means that using the older Defer20220824Handler will not use the default stream merge function and will instead truncate the streamed array on the first chunk.

Patch Changes

• #​12884 d329790 Thanks @​phryneas! - Ensure that PreloadedQueryRef instances are unsubscribed when garbage collected

• #​13086 1a1d408 Thanks @​phryneas! - Change the returned value from null to {} when all fields in a query were skipped.

  This also fixes a bug where useSuspenseQuery would suspend indefinitely when all fields were skipped.

• #​13010 7627000 Thanks @​jerelmiller! - Fix an issue where errors parsed from incremental chunks in ErrorLink might throw when using the GraphQL17Alpha9Handler.

• #​12927 45ebb52 Thanks @​jerelmiller! - Deduplicate watches created by useFragment, client.watchFragment, and cache.watchFragment that contain the same fragment, variables, and identifier. This should improve performance in situations where a useFragment or a client.watchFragment is used to watch the same object in multiple places of an application.

• #​12927 259ae9b Thanks @​jerelmiller! - Allow FragmentType not only to be called as FragmentType<TData>, but also as FragmentType<TypedDocumentNode>.

• #​12925 5851800 Thanks @​jerelmiller! - Fix an issue where calling fetchMore with @defer or @stream would not rerender incremental results as they were streamed.

• #​12927 9e55188 Thanks @​jerelmiller! - Truncate @stream arrays only on last chunk by default.

• #​13083 f3c2be1 Thanks @​phryneas! - Expose the ExtensionsWithStreamInfo type for extensions in Cache.writeQuery, Cache.write and Cache.update so other cache implementations also can correctly access them.

• #​12923 94ea3e3 Thanks @​jerelmiller! - Improve the cache data loss warning message when existing or incoming is an array.

• #​12927 4631175 Thanks @​jerelmiller! - Ignore top-level data values on subsequent chunks in incremental responses.

• #​12927 2be8de2 Thanks @​jerelmiller! - Create mechanism to add experimental features to Apollo Client

• #​12927 96b531f Thanks @​jerelmiller! - Ensure LocalState doesn't try to read from the cache when using a no-cache fetch policy.

• #​12927 bb8ed7b Thanks @​jerelmiller! - Ensure an error is thrown when @stream is detected and an incrementalDelivery handler is not configured.

• #​13053 23ca0ba Thanks @​phryneas! - Use memoized observable mapping when using watchFragment, useFragment or useSuspenseFragment.

• #​12927 44706a2 Thanks @​jerelmiller! - Add helper type QueryRef.ForQuery<TypedDocumentNode>

• #​13082 c257418 Thanks @​phryneas! - Pass streamInfo through result extensions as a WeakRef.

• #​12927 4631175 Thanks @​jerelmiller! - Fix the Defer20220824Handler.SubsequentResult type to match the FormattedSubsequentIncrementalExecutionResult type in graphql@17.0.0-alpha.2.

• #​12927 96b531f Thanks @​jerelmiller! - Warn when using a no-cache fetch policy without a local resolver defined. no-cache queries do not read or write to the cache which meant no-cache queries are silently incomplete when the @client field value was handled by a cache read function.

• #​12927 5776ea0 Thanks @​jerelmiller! - Update the accept header used with the GraphQL17Alpha9Handler to multipart/mixed;incrementalSpec=v0.2 to ensure the newest incremental delivery format is requested.

• #​12927 45ebb52 Thanks @​jerelmiller! - DeepPartial<Array<TData>> now returns Array<DeepPartial<TData>> instead of Array<DeepPartial<TData | undefined>>.

• #​13071 99ffe9a Thanks

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[relativeci]

#1770 Bundle Size — 2.01MiB (-0.06%).

953b18d(current) vs 8961f38 main#1758(baseline)

Important

Bundle introduced 1 duplicate package – View changed duplicate packages

Bundle metrics   7 changes 3 regressions 1 improvement

	Current #1770	Baseline #1758
Initial JS	1.73MiB(-0.05%)	1.73MiB
Initial CSS	0B	0B
Cache Invalidation	86.59%	0%
Chunks	5	5
Assets	235	235
Modules	1529(+0.13%)	1527
Duplicate Modules	135(+0.75%)	134
Duplicate Code	5.7%(-0.18%)	5.71%
Packages	180(+0.56%)	179
Duplicate Packages	12(+9.09%)	11

Bundle size by type   2 changes 2 improvements

	Current #1770	Baseline #1758
JS	1.73MiB (-0.05%)	1.73MiB
Other	250.99KiB (-0.09%)	251.23KiB
IMG	35.85KiB	35.85KiB
HTML	857B	857B

Bundle analysis report Branch renovate/all-dev Project dashboard

---

^{Generated by RelativeCI Documentation Report issue}

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: development/client-angular/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @angular-devkit/build-angular@17.3.17
npm error Found: typescript@5.9.3
npm error node_modules/typescript
npm error   dev typescript@"5.9.3" from the root project
npm error   peerOptional typescript@">=4.9.5" from cosmiconfig@9.0.0
npm error   node_modules/cosmiconfig
npm error     cosmiconfig@"^9.0.0" from postcss-loader@8.1.1
npm error     node_modules/postcss-loader
npm error       postcss-loader@"8.1.1" from @angular-devkit/build-angular@17.3.17
npm error       node_modules/@angular-devkit/build-angular
npm error         dev @angular-devkit/build-angular@"17.3.17" from the root project
npm error   3 more (ts-node, tslint, tsutils)
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=5.2 <5.5" from @angular-devkit/build-angular@17.3.17
npm error node_modules/@angular-devkit/build-angular
npm error   dev @angular-devkit/build-angular@"17.3.17" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.4.5
npm error node_modules/typescript
npm error   peer typescript@">=5.2 <5.5" from @angular-devkit/build-angular@17.3.17
npm error   node_modules/@angular-devkit/build-angular
npm error     dev @angular-devkit/build-angular@"17.3.17" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-01-31T09_49_31_683Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-01-31T09_49_31_683Z-debug-0.log

[pkg-pr-new]

npm i https://pkg.pr.new/apollographql/apollo-client-devtools@1412

npm i https://pkg.pr.new/apollographql/apollo-client-devtools/@apollo/client-devtools-vscode@1412

commit: 953b18d