are you in dev mode and seeing compilation happening, or in production mode after a build?

I've noticed this behavior in dev mode, due to compilation, but not after building for production, where it goes away

create a loading.tsx inside /app/example

not /app, but /app/example

the OP of the linked post is using loading.tsx wrong

idk about your case though

In production too

Why in example? I tried adding loading to root but doesn’t work

/example page requires time to fetch the data, that is the cause of this issue

the time it can render instantly is thanks to soft navigation

and to display loading state for that page, you use app/example/loading.tsx

app/loading.tsx is the loading state for /

So example route is the standard? Seems so weird

The docs doesn’t specify this though

what standard?

there is literally a whole page dedicated to loading states

I mean why must I put it in example folder?

I tried this. It doesn’t load

i'm speaking about the post you linked. they do data fetching in /example. that is why you have to put loading.tsx inside app/example. if you do data fetching in /dashboard you have to put it in app/dashboard and so on

LMAO

Ok

I’ll try again

you never said anything about your own code, you simply said "Im facing the exact same issue as him", how am I supposed to know what route you use to fetch data?