Remove unnecessary router.refresh() usage

[karlhorky]

Since Next.js 13.4.6, calling cookies().set() in a Server Action invalidates the client cache:

• [Bug] next/link is not calling the server for subsequent navigations on dynamic routes  vercel/next.js#42991 (comment)
• PR Invalidate client cache when cookies have changed in Server Actions vercel/next.js#51290

This means that we no longer need to call router.refresh() anymore, which means we can:

• remove the router.refresh() in the logout button Client Component and remove the logout Client Component
• remove the router.refresh() in the FruitCommentForm Client Component

[Josehower]

LGTM!

scheduled to merge on 18th

[ProchaLu]

we found an issue with this: cookies().set(...) no longer clears the client cache starting in next@13.4.11-canary.1 :

• cookies().set() doesn't invalidate client cache vercel/next.js#53261

[karlhorky]

@ProchaLu seems like this was fixed with tests:

• PR fixing the problem router: apply server actions in a similar way to router.refresh() vercel/next.js#53373
• PR adding tests Add test for client router state invalidation caused by cookie mutations vercel/next.js#53494

Can you upgrade and test again?

[ProchaLu]

Upgraded my test project and tested cookie(set) and cookie(get) again. Everything works as expected now without refreshing the page.

Screen.Recording.2023-09-14.at.13.35.42.mov