loading.tsx weird behaviour

[stuck vapor]

I'm seeing some extremely weird behaviour with how loading.tsx works with a page using SSR.

Here's a video:
https://gyazo.com/d7f8c745cdd1479dc0bc169684eef309.mp4

[bleak portal]

Post created!

🔎 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)

[stuck vapor]

bumping this

[full star]

Don't ask to ask, just ask!

Please just ask your question directly: https://dontasktoask.com

Requested by Arxk

[turbid elbow]

what

[turbid elbow]

is this build or on dev?

nd thats weird, yeah

do you have another <Suspense > layer inside your page.tsx?

[stuck vapor]

Accidentally clicked on the don’t ask to ask thing lol

[stuck vapor]

It appears to only do it on the production build

Dev is perfectly fine

And nah I don’t have another suspense layer in the page

[turbid elbow]

thats odd honestly

[stuck vapor]

yea

im using trpc, so it uses that to fetch data from the backend

i also saw this similar issue on github:

https://github.com/vercel/next.js/issues/65217

[turbid elbow]

interesting

[stuck vapor]

which is almost EXACTLY my problem, except i dont have generateMetadata in that page

im starting to think that next isnt picking up the trpc calls as an async function

because it seems like a problem only when something that it doesnt recognize is taking a while to load

[stuck vapor]

Downgraded to v14.2.0. Works fine now

🤔