feat: mutate shortcut

[Netail]

As there's a query shortcut, it would be nice to have a mutate shortcut as well. Used in server actions :)

[netlify]

👷 Deploy request for apollo-client-nextjs-docmodel pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	6115c3e

[pkg-pr-new]

npm i https://pkg.pr.new/apollographql/apollo-client-nextjs/@apollo/client-react-streaming@396

npm i https://pkg.pr.new/apollographql/apollo-client-nextjs/@apollo/experimental-nextjs-app-support@396

commit: 6115c3e

[relativeci]

#372 Bundle Size — 1.25MiB (0%).

6115c3e(current) vs c125a08 main#352(baseline)

Warning

Bundle contains 1 duplicate package – View duplicate packages

Bundle metrics   1 change

	Current #372	Baseline #352
Initial JS	1016.91KiB	1016.91KiB
Initial CSS	70B	70B
Cache Invalidation	4.36%	24.97%
Chunks	34	34
Assets	59	59
Modules	636	636
Duplicate Modules	106	106
Duplicate Code	4.66%	4.66%
Packages	26	26
Duplicate Packages	1	1

Bundle size by type  no changes

	Current #372	Baseline #352
JS	1.24MiB	1.24MiB
Other	9.09KiB	9.09KiB
CSS	70B	70B

Bundle analysis report Branch Netail:feat/mutate-shortcut Project dashboard

---

^{Generated by RelativeCI Documentation Report issue}

[phryneas]

Hi @Netail, thank you for the PR!

Before I get this merged, I'll have to do some investigation - I very roughly remember that the behaviour of registerApolloClient in Server Actions changed between versions of Next.js, so I'll have to double-check that everything works as intended there before we get this change in that encourages usage of rAC in server actions. (We never explicitly targeted them until now.)

I hope I can get to that next week, so please have a bit of patience :)

[Netail]

Hi @Netail, thank you for the PR!

Before I get this merged, I'll have to do some investigation - I very roughly remember that the behaviour of registerApolloClient in Server Actions changed between versions of Next.js, so I'll have to double-check that everything works as intended there before we get this change in that encourages usage of rAC in server actions. (We never explicitly targeted them until now.)

I hope I can get to that next week, so please have a bit of patience :)

That's completely fine, please let me know, we current use getClient().mutate with NextJS 14.2.x without issues, but could ofc be different with Next 15 :)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6115c3e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

Name	Type
@apollo/client-react-streaming	Patch
@apollo/experimental-nextjs-app-support	Patch

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Netail]

Before I get this merged, I'll have to do some investigation - I very roughly remember that the behaviour of registerApolloClient in Server Actions changed between versions of Next.js, so I'll have to double-check that everything works as intended there before we get this change in that encourages usage of rAC in server actions. (We never explicitly targeted them until now.)

Not only in server-actions btw, you could also use mutate in API routes (route.ts files)

[vercel]

@Netail is attempting to deploy a commit to the Apollo Client - Next package - integration tests Team on Vercel.

A member of the Team first needs to authorize it.

[phryneas]

Not only in server-actions btw, you could also use mutate in API routes (route.ts files)

Oh gosh, honestly that sounds dangerous - it would be akin to mutating in GET REST endpoints - imagine the user has their browser set to auto-refresh the page regularly and it causes things to get mutated on the server all the time, or imagine a web crawler hits that mutation.

[Netail]

Oh gosh, honestly that sounds dangerous - it would be akin to mutating in GET REST endpoints - imagine the user has their browser set to auto-refresh the page regularly and it causes things to get mutated on the server all the time, or imagine a web crawler hits that mutation.

Not that easily hahaha, there should be some logic beforehand (maybe some validation and/or authorization), also can be set on different HTTP methods. But it was just an example of where such mutation function could be used. It's already possible ofc, with getClient().mutate

[phryneas]

Yeah, it's possible, I'm just not sure if it should be easily possible 😅

On a sidenote: I'm sorry that this is taking so long - our team got a bit smaller end of last year and while my focus is very much on this repo right now, conceptually it's very far away from Next server actions - I'm working on the React Router and TanStack Start integrations.
So thank you for the patience and I'm sorry, but it will be some time until I can really get back to this.

[Netail]

So thank you for the patience and I'm sorry, but it will be some time until I can really get back to this.

No problem, take your time :)