Showing React.Suspense fallback component works only on initial page render (not the same like in v6)

[griffin94]

Reproduction

Expected Behavior ("react-router-dom": "^6.30.2")
https://codesandbox.io/p/devbox/happy-buck-ld5mh2

Wrong Behavior / Other than on v6 ("react-router": "7.11.0")
https://codesandbox.io/p/devbox/upbeat-julien-77xxtg

System Info

System:
    OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
    CPU: (2) x64 AMD EPYC
    Memory: 984.72 MB / 4.01 GB
    Container: Yes
    Shell: Unknown
  Binaries:
    Node: 20.12.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.5.0 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/share/npm-global/bin/pnpm
  npmPackages:
    vite: ^6.0.3 => 6.3.5

Used Package Manager

npm

Expected Behavior

When I enter the page, I see the "Loader..." inscription. After 2 seconds, when data is ready, "Loader..." inscription disappears and I see list of user. Then I seek for "john" name, hit button and I see "Loader..." again. This is what I expect to be.

So I see Loader

• when I enter the page (initial render)
• whenever I submit Form Component which triggers loader function.

Actual Behavior

When you change dependency from react-router-dom@6.30.2 to react-router@7 it doesn't work the same way. I can see "Loader..." only on initial render.
Example code below:
https://codesandbox.io/p/devbox/upbeat-julien-77xxtg
I think every time loader function returns promise,
I should see React.Suspense fallback component, but now I cannot. If it is not a bug then how to achieve the same result like in v6?

[bilalkib]

@griffin94 This is expected behavior in the latest React Router versions. The loader data is preserved during same-route navigations (e.g., when search parameters like q change), so <Suspense> won’t automatically show its fallback on parameter changes.

You can handle this using useNavigation() to detect the current transition state (idle, loading, or submitting) and render a fallback manually.

I created a small fork demonstrating this behavior and a working solution:
https://codesandbox.io/p/devbox/compassionate-surf-8zwl87

[griffin94]

@bilalkib thank you for your answer, I appreciate it.