`RouteOptions.pendingMs` does not seem to have any effect.

[sookmax]

Which project does this relate to?

Router

Describe the bug

Hey guys, I was trying to use RouteOptions.pendingMs in one of my FileRoute that contains beforeLoad(), and noticed the option doesn't seem to have any effect—i.e., pendingComponent is shown immediately no matter the value provided to pendingMs (0 or 100000).

This is also the case for RouteOptions.loader() as well.

Your Example Website or App

https://stackblitz.com/edit/vitejs-vite-omuhov?file=src%2Froutes%2Findex.tsx

Steps to Reproduce the Bug or Issue

1. refresh the preview browser on the right in the stackblitz sandbox at '/'
2. see if 'Loading...' text is shown immediately after the refresh
3. check pendingMs in src/routes/index.tsx is 1000000
4. do the same for '/about' route (for beforeLoad() case)

Expected behavior

When RouteOptions.pendingMs is specified, the pendingComponent should not be shown unless the loader or beforeLoad takes longer than specified pendingMs.

Screenshots or Videos

No response

Platform

• OS: macOS
• Browser: Chrome
• Version: 130.0.6723.70

Additional context

No response

[MTG2000]

I'm facing the same issue.
Have you managed to find a fix or the root cause of it?

[pascalmtts]

Experiencing the same issue. defaultPendingMs has an effect, but the pendingMs for a route not. @tannerlinsley

[jprosevear]

Not clear to me that defaultPendingMs has an effect either

[jprosevear]

router/packages/react-router/src/Match.tsx

Line 86 in 5099513

<ResolvedSuspenseBoundary fallback={pendingElement}>

appears to be what shows the pending element immediately (ie when refreshing the page) no matter the pending timeout state

Possibly only a problem on first load.

Notes:
#2183 (comment)
#3070

[flodaniel]

Possibly only a problem on first load.

I can confirm that this is only a thing on first load.
My question is what else router should show given that this is the initial load? Isn't the pendingComponent better than nothing at all?

[jprosevear]

Possibly only a problem on first load.

I can confirm that this is only a thing on first load. My question is what else router should show given that this is the initial load? Isn't the pendingComponent better than nothing at all?

The problem is that it shows even if the pendingMs threshold is not hit (like every other transition post initial load) and you have to pay the pendingMinMs penalty.