Describe the bug
when hard-loading a page for the first time, it will show the loader (or an empty page) for the pendingMinMs time even if the route has no loader at all or the loader resolves before pendingMs has expired (default 1 second).
This is not the case when navigating to a route
Your Example Website or App
https://stackblitz.com/edit/tanstack-router-hzdror?file=src%2Fmain.tsx&preset=node
Steps to Reproduce the Bug or Issue
- reload the sandbox on the
Home tab (this route has no loader)
- you should see an empty page for 5 seconds.
- if you comment in the
defaultPendingComponent, you should see loading... for 5 seconds.
- now go to the
about tab (which has a 500ms loader, so shorter than the default 1s pendingMs) and reload it.
- you should, again see the
loading... (or an empty screen) for 5 seconds
- now navigate to
Home via the link
- home loads instantly, as expected, because it has no loader.
Expected behavior
I'd expect pendingMinMs to not influence the hard reload times, just like it doesn't block navigations either.
Screenshots or Videos
No response
Platform
any
Additional context
This behaviour is observable even with the default settings, but because defaultPendingMinMs is "just" 500ms, it's harder to spot.
Describe the bug
when hard-loading a page for the first time, it will show the loader (or an empty page) for the
pendingMinMstime even if the route has no loader at all or the loader resolves beforependingMshas expired (default 1 second).This is not the case when navigating to a route
Your Example Website or App
https://stackblitz.com/edit/tanstack-router-hzdror?file=src%2Fmain.tsx&preset=node
Steps to Reproduce the Bug or Issue
Hometab (this route has no loader)defaultPendingComponent, you should seeloading...for 5 seconds.abouttab (which has a 500ms loader, so shorter than the default 1spendingMs) and reload it.loading...(or an empty screen) for 5 secondsHomevia the linkExpected behavior
I'd expect
pendingMinMsto not influence the hard reload times, just like it doesn't block navigations either.Screenshots or Videos
No response
Platform
any
Additional context
This behaviour is observable even with the default settings, but because
defaultPendingMinMsis "just" 500ms, it's harder to spot.