@apollo/client - npm Package Versions

3.11.0-rc.0

Minor Changes

• #11923 d88c7f8 Thanks @jerelmiller! - Add support for subscribeToMore function to useQueryRefHandlers.

• #11854 3812800 Thanks @jcostello-atlassian! - Support extensions in useSubscription

• #11923 d88c7f8 Thanks @jerelmiller! - Add support for subscribeToMore function to useLoadableQuery.

• #11863 98e44f7 Thanks @phryneas! - Reimplement useSubscription to fix rules of React violations.

• #11869 a69327c Thanks @phryneas! - Rewrite big parts of useQuery and useLazyQuery to be more compliant with the Rules of React and React Compiler

• #11936 1b23337 Thanks @jerelmiller! - Add the ability to specify a name for the client instance for use with Apollo Client Devtools. This is useful when instantiating multiple clients to identify the client instance more easily. This deprecates the connectToDevtools option in favor of a new devtools configuration.

  new ApolloClient({
    devtools: {
      enabled: true,
      name: "Test Client",
    },
  });
  

  This option is backwards-compatible with connectToDevtools and will be used in the absense of a devtools option.

• #11923 d88c7f8 Thanks @jerelmiller! - Add support for subscribeToMore function to useBackgroundQuery.

• #11789 5793301 Thanks @phryneas! - Changes usages of the GraphQLError type to GraphQLFormattedError.

  This was a type bug - these errors were never GraphQLError instances to begin with, and the GraphQLError class has additional properties that can never be correctly rehydrated from a GraphQL result. The correct type to use here is GraphQLFormattedError.

  Similarly, please ensure to use the type FormattedExecutionResult instead of ExecutionResult - the non-"Formatted" versions of these types are for use on the server only, but don't get transported over the network.

• #11930 a768575 Thanks @jerelmiller! - Deprecates experimental schema testing utilities introduced in 3.10 in favor of recommending @apollo/graphql-testing-library.

Patch Changes

• #11927 2941824 Thanks @phryneas! - Add restart function to useSubscription.

• #11902 96422ce Thanks @phryneas! - Add cause field to ApolloError.

• #11806 8df6013 Thanks @phryneas! - MockLink: add query default variables if not specified in mock request

• #11626 228429a Thanks @phryneas! - Call nextFetchPolicy with "variables-changed" even if there is a fetchPolicy specified. (fixes #11365)

• #11719 09a6677 Thanks @phryneas! - Allow wrapping createQueryPreloader

• #11921 70406bf Thanks @phryneas! - add ignoreResults option to useSubscription

3.10.8

Patch Changes

• #11911 1f0460a Thanks @jerelmiller! - Allow undefined to be returned from a cache.modify modifier function when a generic type argument is used.

3.10.7

Patch Changes

• #11901 10a8c0a Thanks @phryneas! - update canUseLayoutEffect check to also allow for layout effects in React Native

• #11861 1aed0e8 Thanks @henryqdineen! - Defend against non-serializable params in invariantWrappers

• #11905 29755da Thanks @phryneas! - Add .d.cts files for cjs bundles

• #11906 d104759 Thanks @phryneas! - chore: update TypeScript to 5.5

3.10.6

Patch Changes

• #11900 f745558 Thanks @phryneas! - useMutation: use useIsomorphicLayoutEffect instead of useLayoutEffect

3.10.5

Patch Changes

• #11888 7fb7939 Thanks @phryneas! - switch useRenderGuard to an approach not accessing React's internals

• #11511 6536369 Thanks @phryneas! - useLoadableQuery: ensure that loadQuery is updated if the ApolloClient instance changes

• #11860 8740f19 Thanks @alessbell! - Fixes #11849 by reevaluating window.fetch each time BatchHttpLink uses it, if not configured via options.fetch. Takes the same approach as PR #8603 which fixed the same issue in HttpLink.

• #11852 d502a69 Thanks @phryneas! - Fix a bug where calling the useMutation reset function would point the hook to an outdated client reference.

• #11329 3d164ea Thanks @PaLy! - Fix graphQLErrors in Error Link if networkError.result is an empty string

• #11852 d502a69 Thanks @phryneas! - Prevent writing to a ref in render in useMutation. As a result, you might encounter problems in the future if you call the mutation's execute function during render. Please note that this was never supported behavior, and we strongly recommend against it.

• #11848 ad63924 Thanks @phryneas! - Ensure covariant behavior: MockedResponse<X,Y> should be assignable to MockedResponse

• #11851 45c47be Thanks @phryneas! - Avoid usage of useRef in useInternalState to prevent ref access in render.

• #11877 634d91a Thanks @phryneas! - Add missing name to tuple member (fix TS5084)

• #11851 45c47be Thanks @phryneas! - Fix a bug where useLazyQuery would not pick up a client change.