Skip to content

patch: unstable traverse cache#15288

Open
jacob-ebey wants to merge 1 commit into
mainfrom
unstable_traverseCache
Open

patch: unstable traverse cache#15288
jacob-ebey wants to merge 1 commit into
mainfrom
unstable_traverseCache

Conversation

@jacob-ebey

@jacob-ebey jacob-ebey commented Jul 7, 2026

Copy link
Copy Markdown
Member

Add the future.unstable_traverseCache flag to set client payload fetch cache behavior based on navigation type.

  • Back/forward traversals use cache: "force-cache" for .data/.rsc payload requests when enabled.
  • Other navigations and fetchers use cache: "default" when enabled.
  • true enables it only in production
  • force enables it in production and development

@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Preview Build Available

Preview builds have been created for this PR. You can install react-router using:

pnpm install "remix-run/react-router#preview/pr-15288&path:packages/react-router"

And/or install other packages via:

pnpm install "remix-run/react-router#preview/pr-15288&path:packages/react-router-dev"
pnpm install "remix-run/react-router#preview/pr-15288&path:packages/react-router-express"
pnpm install "remix-run/react-router#preview/pr-15288&path:packages/react-router-node"
pnpm install "remix-run/react-router#preview/pr-15288&path:packages/react-router-serve"

These preview builds will be updated automatically as you push new commits.

@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

✅ CLA Signed

Thanks for signing the Contributor License Agreement.

@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

✅ Change File Found

One or more change files found.

Type Change
unstable Add the future.unstable_traverseCache flag to set client payload fetch cache behavior based on navigation type.
unstable Add the future.unstable_traverseCache flag to set client payload fetch cache behavior based on navigation type.

Add the `future.unstable_traverseCache` flag to set client payload fetch
cache behavior based on navigation type.

- Back/forward traversals use `cache: "force-cache"` for `.data`/`.rsc`
  payload requests when enabled.
- Other navigations and fetchers use `cache: "default"` when enabled.
- `true` enables it only in production
- `force` enables it in production and development
@jacob-ebey jacob-ebey force-pushed the unstable_traverseCache branch from 950367a to 875e246 Compare July 7, 2026 00:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant