Relay and Next13
- Dominant language
- Rust
- Stars
- 19k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
Hello 👋
This is a follow up on #3889
Next13 ships with a new way to load data on the server and client:
- **build in relay** support (from Next12)
- reacts [monkey patched](https://github.com/facebook/react/blob/28a574ea8f5d0efa95f861abca26a67af47dd0c0/packages/react/src/ReactFetch.js#L124) global fetch method
- react [server components](https://beta.nextjs.org/docs/data-fetching/fetching)
- a new [folder structure for creating routes](https://beta.nextjs.org/docs/routing/fundamentals)

Could you please share your opinions and visions if/how relay might fit in here?
Does it make sense to use Relay at all for Next13 Server Components?
Does it make sense to use Relay for Next13 app layout and app pages?
Will reacts fetch cache work well with relays cache?
Contributor guide
Research direction
Start with the follow-up issue #3889 and the linked Next13 documentation on data fetching and routing. Compare Relay’s server and client data-loading model with Next13 Server Components, app layouts, app pages, and React fetch caching; done would be a documented decision or design direction, not a code change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, next.js, react
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100