You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 aThis 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/1I 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.
The text was updated successfully, but these errors were encountered: