apollographql / apollographql/apollo-client-integrations
Prefetching Data within RSCs
- Dominant language
- TypeScript
- Stars
- 556
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Hey, I've been taking a peek at how Apollo should be working with Next 13's app directory and found this comment: https://github.com/apollographql/apollo-client-nextjs/pull/9#issuecomment-1544005482 chatting a bit more around prefetching within server components and pushing that to client components. In the spirit of allowing for easier migration paths from the pages directory -> app directory we'd really like to use prefetching initially both at the layout level and page level so that we can more easily shift things over.
Has there been any movement around supporting page level prefetching and population to client components? It seems like layout level I should be able to forward the data over as props to the client component and then initialize my cache with it.
Thanks for all the awesome work supporting Next 13!
Contributor guide
No contributing guide indexed for this repository
Research direction
Begin with the linked pull-request comment and the Next 13 app directory/server-component context. No source files or tests are identified; clarify how page- and layout-level prefetching should populate client components and define completion around supported data transfer and cache initialization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, next.js, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100