Chapter 8: Question to the use of unstable_noStore() inside data access functions.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.8k
- Forks
- 2.2k
- PR merge metrics
- No merged PRs in 30d
Description
Hi all,
From the docs:
unstable_noStore can be used to declaratively opt out of static rendering and indicate a particular component should not be cached.
In the tutorial, we use unstable_noStore() inside data access functions. Not inside components, as the docs imply. Basically, we force components, using the data access functions, to dynamic rendering.
Wouldn't it be better to make this behavior explicit at the component level in @/app/dashboard/page.tsx?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the tutorial's use of unstable_noStore() in its data access functions with the linked Next.js documentation. Inspect @/app/dashboard/page.tsx and the referenced data access functions first; this is done when the tutorial's behavior and guidance consistently match the documented placement, with the issue's question resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- next.js, typescript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100