apollo

wrote the variables commit and its busy flag separately, under Vue 3.6 watchers are triggered sync during write and could catch half-committed state.

Adds @vue/apollo-components: ApolloQuery, ApolloMutation, ApolloSubscription, ApolloSubscribeToMore and ApolloFragment, built on @vue/apollo-composable and sharing the same client. The docs now cover both APIs side by side. Also fixes two composable bugs the components turned up.

Describe the bug In 's input normalization, a plain argument is deep-wrapped in a Vue reactive proxy before it reaches Apollo Client, so the document Apollo receives is not the object the caller passed. The cause is here (current tip): https://github.com/vuejs/apollo/blob/69d9097548a3/packages/vue-apollo-composable/src/useQuery.ts#L968 For the most common documented call form, , falls through to , and deep-converts objects — so is , not . Reproduction Observed on with 4.2.3 and Vue 3.5; the normalization is unchanged at the current tip (69d9097). Why this matters 1. Document identity is load-bearing in Apollo Client. Per-document caches (document transform cache, cache) are WeakMaps keyed by object reference. The proxy and the raw constant are different keys, so the same operation used both through and directly (, , SSR code) is transformed and printed separately. 2. Identity-based matching can silently miss. APIs that match operations by document — e.g. after a mutation — see a different object than the one the observable query was registered with, since each is routed through the transform cache under its own key. 3. Needless reactivity overhead. Every AST node Apollo touches while transforming/printing the document is tracked as a dependency of a proxy that will never mutate. Suggested fix Normalize with a getter instead of , which supports the same input surface but never converts the returned value, preserving referential identity for plain constants, refs, and getters alike: Happy to send a PR if this shape is acceptable. Workaround Pass a getter: — wraps getters in a non-converting readonly ref, so identity is preserved. Context Found while porting a production React + Apollo Client 4 app to Vue 3.5 against the v5 alpha — an Apollo-level parity test suite flagged the identity loss.