#Suspense doesn't show fallback on page reload in prod but it works in dev
15 messages · Page 1 of 1 (latest)
🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord
🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize
✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)
Hi, I have the completely oposite problem. Hard reload shows the suspense correctly but client navigation triggers the closest loading.tsx, I feel like everytime I start doing something with app router everything behaves differently...
@regal cape loading.tsx will never show up for refreshing, its mentioned in the docs that its only and only for navigation.
I know this, but in the example the client navigation still triggers the suspense
After all loading.{tsx,jsx} is just a suspense over the whole page
@toxic gazelle im not sure why your suspense isnt running for refreshing.. can you record all the stuff? both dev and prod
loading.tsx is suspense... yes. But its diff from react suspense... hence why it wont show on refreshing... why this is a case you can just dig in the source code.
We are assuming ppr fixes this.. if it even is a bug.. but yea suspense will always show.. loading will only show on navigation.
Will dig in the source, thanks for the support 👍
np, tbf loading and suspense.. is goofy atm
i agree on that
we can just accept and move on :D
so in this video you can see suspense working in dev mode, in prod nothing happens the page just reloads without the fallback component
oh it somehow works now even tho i didnt change anything