SPA Mode should not use Single Fetch revalidation behavior

[brophdawg11]

The Single Fetch revalidation behavior (de-optimization) is incorrectly being applied when in SPA mode and there is no "single fetch" to the server. SPA Mode should receive the default revalidation behavior optimizations where parent routes do not revalidate on GET navigations by default (unless path params or search params change)

I'm using React Router as a...

framework

Reproduction

• Create an app in SPA mode (ssr: false) suing nested routes with loaders.
• Route from one child route to another (/parent/a -> /parent/b)

Expected Behavior

The parent loader should not re-run by default

Actual Behavior

The parent loader should re-runs by default

[mrtinsvitor]

This looks similar to the issue I was having, #12427. Would be great if it could get fixed 🙏

[nakah]

Same issue here. However, as I'm using react-query inside the clientLoader, no query is sent to the network thanks to its internal caching mecanism.

[brophdawg11]

This is fixed by #12948 and will be available in the next release

[github-actions]

🤖 Hello there,

We just published version 7.2.0 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!

[github-actions]

🤖 Hello there,

We just published version 7.3.0 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!