Skip to content
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

Using a detail page results in exception #13

Open
mastoj opened this issue Nov 10, 2023 · 1 comment
Open

Using a detail page results in exception #13

mastoj opened this issue Nov 10, 2023 · 1 comment

Comments

@mastoj
Copy link

mastoj commented Nov 10, 2023

Not sure where you want issues like this, so I add it here and then it can be moved somewhere else.

I started playing with the sample, and to make it more realistic I created a /[id] route and just copied the page.tsx there as well. For some reason I get a This page needs to bail out of prerendering at this point because it used revalidate: 0. React throws this special object to indicate where. It should not be caught by your own try/catch. error when I run on vercel even thought it works perfectly fine locally. The specific code change can be found here: mastoj@04f0476, and the deployed app: https://next-partial-prerendering-ten.vercel.app/1

I also don't understand why my timestamps that I added is first rendered statically and then also re-rendered, in my head static content shouldn't change.

@z4nr34l
Copy link

z4nr34l commented Jan 25, 2024

Same issue here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants