New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[appDir][Dynamic Rendering] Dynamic Data Fetching doesn't seem to be fully working (various bugs in Data Fetching & Route Segment Config Options) #42856
Comments
It seems that the current tests are KO ( |
Same for me! |
@gfortaine we will look into this. For future reference, please refrain from mass tagging core maintainers. 🙏 💚 |
@balazsorban44 As a side note, it seems that the bug appears only in production mode ( |
Encountering the same thing, the I've tested as well that A quick note for those using preview mode though, you can't make it work with |
Same for me. For me, I also wonder whether At least according to the document, I think expected behavior of |
@gfortaine fyi
|
Hello! Did you manage to solve this using 13.1.1? |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Verify canary release
Provide environment information
What browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
Describe the Bug
It seems that we have had a hard time setting up Dynamic Rendering. Indeed, it looks like that many of the various options are still KO at the time of writing :
Route Segment Config Options
dynamic
with'force-dynamic'
&fetchCache
with'default-no-store'
didn't workDynamic Data Fetches
{ cache: 'no-store' }
&{ next: { revalidate: 0 } }
didn't work neitherAt the end of the day, only
revalidate
with a value of0
did the trickExpected Behavior
Options to enable Dynamic Rendering described in the documentation should work :
https://beta.nextjs.org/docs/rendering/static-and-dynamic-rendering#dynamic-rendering
Link to reproduction - Issues with a link to complete (but minimal) reproduction code will be addressed faster
https://github.com/vercel/next-react-server-components
To Reproduce
Clone the repo and use the various options (except
revalidate
with a value of0
that is working) in theItemPage
Server Component (/app/item/page.js
). Then, you will see the bug when trying to go on the/item
page with the following error message :An item with an ID must be provided as a query parameter.
The text was updated successfully, but these errors were encountered: