[ { "path": ".browserslistrc", "content": "# Browsers we support\nChrome >= 73\nChromeAndroid >= 75\nFirefox >= 67\nEdge >= 17\nSafari >= 12.1\niOS >= 11.3\n" }, { "path": ".changeset/README.md", "content": "# Changesets\n\nHello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works\nwith multi-package repos, or single-package repos to help you version and publish your code. You can\nfind the full documentation for it [in our repository](https://github.com/changesets/changesets)\n\nWe have a quick list of common questions to get you started engaging with this project in\n[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)\n" }, { "path": ".changeset/config.json", "content": "{\n \"$schema\": \"https://unpkg.com/@changesets/config@2.0.0/schema.json\",\n \"changelog\": [\n \"@remix-run/changelog-github\",\n { \"repo\": \"remix-run/react-router\" }\n ],\n \"commit\": false,\n \"fixed\": [\n [\n \"create-react-router\",\n \"react-router\",\n \"react-router-dom\",\n \"@react-router/architect\",\n \"@react-router/cloudflare\",\n \"@react-router/dev\",\n \"@react-router/fs-routes\",\n \"@react-router/express\",\n \"@react-router/node\",\n \"@react-router/remix-routes-option-adapter\",\n \"@react-router/serve\"\n ]\n ],\n \"linked\": [],\n \"access\": \"public\",\n \"baseBranch\": \"dev\",\n \"updateInternalDependencies\": \"patch\",\n \"bumpVersionsWithWorkspaceProtocolOnly\": true,\n \"ignore\": [\"integration\", \"integration-*\", \"@playground/*\"],\n \"___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH\": {\n \"onlyUpdatePeerDependentsWhenOutOfRange\": true\n }\n}\n" }, { "path": ".eslintignore", "content": "/fixtures/\nnode_modules/\npnpm-lock.yaml\n/docs/api\nexamples/**/dist/\nworker-configuration.d.ts\n/playground/\n/playground-local/\nintegration/helpers/**/dist/\nintegration/helpers/**/build/\nplaywright-report/\ntest-results/\nbuild.utils.d.ts\n.wrangler/\n.tmp/\n.react-router/\npackages/**/dist/\npackages/react-router-dom/server.d.ts\npackages/react-router-dom/server.js\npackages/react-router-dom/server.mjs\ntutorial/dist/\npublic/\n" }, { "path": ".eslintrc", "content": "{\n \"extends\": [\"react-app\"],\n \"rules\": {\n \"import/first\": \"off\",\n \"@typescript-eslint/consistent-type-imports\": \"error\"\n },\n \"overrides\": [\n {\n \"files\": [\"**/__tests__/**\"],\n \"plugins\": [\"jest\"],\n \"extends\": [\"plugin:jest/recommended\"]\n },\n {\n \"files\": [\"integration/**/*.*\"],\n \"rules\": {\n \"react-hooks/rules-of-hooks\": \"off\"\n },\n \"env\": {\n \"jest/globals\": false\n }\n },\n {\n \"files\": [\"packages/react-router-dev/config/default-rsc-entries/*\"],\n \"rules\": {\n \"@typescript-eslint/consistent-type-imports\": \"off\"\n }\n },\n {\n // Only apply JSDoc lint rules to files we auto-generate docs for\n \"files\": [\n \"packages/react-router/lib/components.tsx\",\n \"packages/react-router/lib/hooks.tsx\",\n \"packages/react-router/lib/dom/lib.tsx\",\n \"packages/react-router/lib/dom/ssr/components.tsx\",\n \"packages/react-router/lib/dom/ssr/server.tsx\",\n \"packages/react-router/lib/dom-export/hydrated-router.tsx\",\n \"packages/react-router/lib/dom/server.tsx\",\n \"packages/react-router/lib/router/utils.ts\",\n \"packages/react-router/lib/rsc/browser.tsx\",\n \"packages/react-router/lib/rsc/server.rsc.ts\",\n \"packages/react-router/lib/rsc/server.ssr.tsx\",\n \"packages/react-router/lib/rsc/html-stream/browser.ts\",\n ],\n \"plugins\": [\"jsdoc\"],\n \"rules\": {\n \"jsdoc/check-access\": \"error\",\n \"jsdoc/check-alignment\": \"error\",\n \"jsdoc/check-param-names\": \"error\",\n \"jsdoc/check-property-names\": \"error\",\n \"jsdoc/check-tag-names\": [\n \"error\",\n {\n \"definedTags\": [\"additionalExamples\", \"category\", \"mode\"]\n }\n ],\n \"jsdoc/no-defaults\": \"error\",\n \"jsdoc/no-multi-asterisks\": [\"error\", { \"allowWhitespace\": true }],\n \"jsdoc/require-description\": \"error\",\n \"jsdoc/require-param\": [\"error\", { \"enableRootFixer\": false }],\n \"jsdoc/require-param-description\": \"error\",\n \"jsdoc/require-param-name\": \"error\",\n \"jsdoc/require-returns\": \"error\",\n \"jsdoc/require-returns-check\": \"error\",\n \"jsdoc/require-returns-description\": \"error\",\n \"jsdoc/sort-tags\": [\n \"error\",\n {\n \"tagSequence\": [\n {\n \"tags\": [\"description\"]\n },\n {\n \"tags\": [\"example\"]\n },\n {\n \"tags\": [\"additionalExamples\"]\n },\n {\n \"tags\": [\n \"name\",\n \"public\",\n \"private\",\n \"category\",\n \"mode\",\n \"param\",\n \"returns\"\n ]\n }\n ]\n }\n ]\n }\n }\n ],\n \"reportUnusedDisableDirectives\": true\n}\n" }, { "path": ".github/FUNDING.yml", "content": "# These are supported funding model platforms\n\ngithub: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]\npatreon: # Replace with a single Patreon username\nopen_collective: react-router\nko_fi: # Replace with a single Ko-fi username\ntidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel\ncommunity_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry\nliberapay: # Replace with a single Liberapay username\nissuehunt: # Replace with a single IssueHunt username\notechie: # Replace with a single Otechie username\ncustom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']\n" }, { "path": ".github/ISSUE_TEMPLATE/bug_report.yml", "content": "name: ๐Ÿ› Bug Report\ndescription: Something is wrong with React Router\nlabels:\n - bug\nbody:\n - type: markdown\n attributes:\n value: |\n Thank you for helping to improve React Router!\n\n Please note that **all** bugs must have a **minimal** and **runnable** reproduction, meaning that it is not just pointing to a deployed site or a branch in your existing application, or showing a small code snippet. For more information, please refer to the [Bug/Issue Process Guidelines](https://github.com/remix-run/react-router/blob/main/GOVERNANCE.md#bugissue-process).\n\n ## If you are using **Framework Mode**, you have 2 preferred options\n\n ### Option 1 - Create a failing integration test\n\n ๐Ÿ† The most helpful reproduction is to use our _bug report integration test_ template:\n\n 1. [Fork `remix-run/react-router`](https://github.com/remix-run/react-router/fork)\n 2. Open [`integration/bug-report-test.ts`](https://github.com/remix-run/react-router/blob/dev/integration/bug-report-test.ts) in your editor\n 3. Follow the instructions to create a failing bug report test\n 4. Link to your forked branch with the failing test in this issue\n\n ### Option 2 - Create a **minimal** reproduction\n\n - ๐Ÿฅ‡ Link to a [StackBlitz](https://reactrouter.com/new) environment\n - ๐Ÿฅˆ Link to a GitHub repository containing a minimal reproduction app\n\n ## If you are using **Data** or **Declarative Mode**\n\n Create a **minimal** reproduction\n\n - ๐Ÿฅ‡ Link to a CodeSandbox repro: [TS](https://codesandbox.io/templates/react-vite-ts) | [JS](https://codesandbox.io/templates/react-vite)\n - ๐Ÿฅˆ Link to a GitHub repository containing a minimal reproduction app\n\n - type: textarea\n id: reproduction\n attributes:\n label: Reproduction\n description: Link to reproduction and steps to reproduce the behavior\n placeholder: Go to https://stackblitz.com/edit/... and click the \"Submit\" button\n validations:\n required: true\n - type: textarea\n id: system-info\n attributes:\n label: System Info\n description: Output of `npx envinfo --system --npmPackages '{vite,react-router,@react-router/*}' --binaries --browsers`\n render: shell\n placeholder: System, Binaries, Browsers\n validations:\n required: true\n - type: dropdown\n id: package-manager\n attributes:\n label: Used Package Manager\n description: Select the used package manager\n options:\n - npm\n - yarn\n - pnpm\n validations:\n required: true\n - type: textarea\n attributes:\n label: Expected Behavior\n description: A concise description of what you expected to happen.\n validations:\n required: true\n - type: textarea\n attributes:\n label: Actual Behavior\n description: A concise description of what you're experiencing.\n validations:\n required: true\n" }, { "path": ".github/ISSUE_TEMPLATE/config.yml", "content": "blank_issues_enabled: false\ncontact_links:\n - name: ๐Ÿ’ก Feature Request\n url: https://github.com/remix-run/react-router/discussions/new?category=proposals\n about: If you've got an idea for a new feature in React Router, please open a new Discussion with the `Proposals` label\n - name: ๐Ÿค” Usage Question (Github Discussions)\n url: https://github.com/remix-run/remix/discussions/new?category=q-a\n about: Open a Discussion in GitHub with the `Q&A` label\n - name: ๐Ÿ’ฌ Remix Discord Channel\n url: https://rmx.as/discord\n about: Interact with other people using React Router and Remix ๐Ÿ“€\n" }, { "path": ".github/ISSUE_TEMPLATE/documentation_isse.yml", "content": "name: ๐Ÿ“š Documentation Issue\ndescription: Something is wrong with the React Router docs\ntitle: \"[Docs]: \"\nlabels:\n - docs\nbody:\n - type: markdown\n attributes:\n value: |\n Thank you for contributing!\n\n For documentation updates - we would happily accept PRs, so feel free to update and\n open a PR to the `main` branch. Otherwise let us know in this issue what you felt\n was missing or incorrect.\n\n - type: textarea\n attributes:\n label: Describe what's incorrect/missing in the documentation\n description: A concise description of what you expected to see in the docs\n validations:\n required: true\n" }, { "path": ".github/dependabot.yml", "content": "version: 2\nupdates:\n - package-ecosystem: github-actions\n directory: /\n schedule:\n interval: daily\n" }, { "path": ".github/workflows/close-feature-pr.yml", "content": "# Close a singular pull request that implements a feature that has not\n# gone through the Proposal process\n# Triggered by adding the `feature-request` label to an issue\n\nname: ๐Ÿšช Check Feature PR\n\non:\n pull_request_target:\n types: [labeled]\n\njobs:\n close-feature-pr:\n name: ๐Ÿšช Check Feature PR\n if: github.repository == 'remix-run/react-router' && github.event.label.name == 'feature-request'\n runs-on: ubuntu-latest\n permissions:\n pull-requests: write\n steps:\n - name: โฌ‡๏ธ Checkout repo\n uses: actions/checkout@v6\n\n - name: ๐Ÿšช Close PR\n env:\n GH_TOKEN: ${{ github.token }}\n run: |\n gh pr comment ${{ github.event.pull_request.number }} -F ./scripts/close-feature-pr.md\n gh pr edit ${{ github.event.pull_request.number }} --remove-label ${{ github.event.label.name }}\n gh pr close ${{ github.event.pull_request.number }}\n" }, { "path": ".github/workflows/close-no-repro-issue.yml", "content": "# Close a singular issue without a reproduction\n# Triggered by adding the `no-reproduction` label to an issue\n\nname: ๐Ÿšช Close issue without a reproduction\n\non:\n issues:\n types: [labeled]\n\njobs:\n close-no-repro-issue:\n name: ๐Ÿšช Close issue\n if: github.repository == 'remix-run/react-router' && github.event.label.name == 'no-reproduction'\n runs-on: ubuntu-latest\n steps:\n - name: โฌ‡๏ธ Checkout repo\n uses: actions/checkout@v6\n\n - name: ๐Ÿšช Close issue\n env:\n GH_TOKEN: ${{ github.token }}\n run: |\n gh issue comment ${{ github.event.issue.number }} -F ./scripts/close-no-repro-issue.md\n gh issue edit ${{ github.event.issue.number }} --remove-label ${{ github.event.label.name }}\n gh issue close ${{ github.event.issue.number }} -r \"not planned\";\n" }, { "path": ".github/workflows/close-no-repro-issues.yml", "content": "# This is a bulk-close script that was used initially to find and close issues\n# without a repro, but moving forward we'll likely use the singular version\n# (close-no-repro-issue.yml) on new issues which is driven by a label added to\n# the issue\n\nname: ๐Ÿšช Close issues without a reproduction\n\non:\n workflow_dispatch:\n inputs:\n dryRun:\n type: boolean\n description: \"Dry Run? (no issues will be closed)\"\n default: false\n\nconcurrency: ${{ github.workflow }}-${{ github.ref }}\n\njobs:\n close-no-repro-issues:\n name: ๐Ÿšช Close issues\n if: github.repository == 'remix-run/react-router'\n runs-on: ubuntu-latest\n env:\n CI: \"true\"\n GH_TOKEN: ${{ github.token }}\n steps:\n - name: โฌ‡๏ธ Checkout repo\n uses: actions/checkout@v6\n\n - name: ๐Ÿ“ฆ Setup pnpm\n uses: pnpm/action-setup@v4.1.0\n\n - name: โŽ” Setup node\n uses: actions/setup-node@v6\n with:\n # required for --experimental-strip-types\n node-version: 22\n cache: \"pnpm\"\n\n - name: ๐Ÿ“ฅ Install deps\n run: pnpm install --frozen-lockfile\n\n - name: ๐Ÿšช Close Issues (Dry Run)\n if: ${{ inputs.dryRun }}\n run: node --experimental-strip-types ./scripts/close-no-repro-issues.ts --dryRun\n\n - name: ๐Ÿšช Close Issues\n if: ${{ ! inputs.dryRun }}\n run: node --experimental-strip-types ./scripts/close-no-repro-issues.ts\n" }, { "path": ".github/workflows/deduplicate-lock-file.yml", "content": "name: โš™๏ธ Deduplicate lock file\n\non:\n push:\n branches:\n - dev\n paths:\n - pnpm-lock.yaml\n\nconcurrency:\n group: ${{ github.workflow }}-${{ github.ref }}\n cancel-in-progress: true\n\njobs:\n dedupe:\n if: github.repository == 'remix-run/react-router'\n runs-on: ubuntu-latest\n\n steps:\n - name: โฌ‡๏ธ Checkout repo\n uses: actions/checkout@v6\n with:\n token: ${{ secrets.FORMAT_PAT }}\n\n - name: ๐Ÿ“ฆ Setup pnpm\n uses: pnpm/action-setup@v4\n\n - name: โŽ” Setup node\n uses: actions/setup-node@v6\n with:\n node-version-file: \".nvmrc\"\n cache: \"pnpm\"\n\n - name: โš™๏ธ Dedupe lock file\n run: pnpm dedupe && rm -rf ./node_modules && pnpm install\n\n - name: ๐Ÿ’ช Commit\n run: |\n git config --local user.email \"hello@remix.run\"\n git config --local user.name \"Remix Run Bot\"\n\n git add .\n if [ -z \"$(git status --porcelain)\" ]; then\n echo \"๐Ÿ’ฟ no deduplication needed\"\n exit 0\n fi\n git commit -m \"chore: deduplicate \\`pnpm-lock.yaml\\`\"\n git push\n echo \"๐Ÿ’ฟ pushed dedupe changes https://github.com/$GITHUB_REPOSITORY/commit/$(git rev-parse HEAD)\"\n" }, { "path": ".github/workflows/docs.yml", "content": "name: ๐Ÿ“š Docs\n\non:\n push:\n branches:\n - main\n - dev\n paths:\n - \"packages/**/*.ts\"\n - \"packages/**/*.tsx\"\n - \"scripts/docs.ts\"\n workflow_dispatch:\n inputs:\n branch:\n description: \"Branch to generate docs on\"\n required: true\n\nconcurrency:\n group: ${{ github.workflow }}-${{ github.ref }}\n cancel-in-progress: true\n\njobs:\n docs:\n if: github.repository == 'remix-run/react-router'\n runs-on: ubuntu-latest\n\n steps:\n - name: โฌ‡๏ธ Checkout repo\n uses: actions/checkout@v6\n with:\n token: ${{ secrets.FORMAT_PAT }}\n ref: ${{ github.event.inputs.branch }}\n\n - name: ๐Ÿ“ฆ Setup pnpm\n uses: pnpm/action-setup@v4\n\n - name: โŽ” Setup node\n uses: actions/setup-node@v6\n with:\n node-version-file: \".nvmrc\"\n cache: pnpm\n\n - name: ๐Ÿ“ฅ Install deps\n run: pnpm install --frozen-lockfile\n\n - name: ๐Ÿ— Build\n run: pnpm build\n\n - name: ๐Ÿ“š Generate Typedoc Docs\n run: pnpm run docs:typedoc\n\n - name: ๐Ÿ“š Generate Markdown Docs\n run: pnpm run docs:jsdoc --write\n\n - name: ๐Ÿ’ช Commit\n run: |\n git config --local user.email \"hello@remix.run\"\n git config --local user.name \"Remix Run Bot\"\n\n git add .\n if [ -z \"$(git status --porcelain)\" ]; then\n echo \"๐Ÿ’ฟ no docs changed\"\n exit 0\n fi\n git commit -m \"chore: generate markdown docs from jsdocs\"\n git push\n echo \"๐Ÿ’ฟ pushed docs changes https://github.com/$GITHUB_REPOSITORY/commit/$(git rev-parse HEAD)\"\n" }, { "path": ".github/workflows/format.yml", "content": "name: ๐Ÿ‘” Format\n\non:\n push:\n branches:\n - main\n - dev\n\nconcurrency:\n group: ${{ github.workflow }}-${{ github.ref }}\n cancel-in-progress: true\n\njobs:\n format:\n if: github.repository == 'remix-run/react-router'\n runs-on: ubuntu-latest\n\n steps:\n - name: โฌ‡๏ธ Checkout repo\n uses: actions/checkout@v6\n with:\n token: ${{ secrets.FORMAT_PAT }}\n\n - name: ๐Ÿ“ฆ Setup pnpm\n uses: pnpm/action-setup@v4\n\n - name: โŽ” Setup node\n uses: actions/setup-node@v6\n with:\n node-version-file: \".nvmrc\"\n cache: pnpm\n\n - name: ๐Ÿ“ฅ Install deps\n run: pnpm install --frozen-lockfile\n\n - name: ๐Ÿ”ƒ Sort contributors.yml\n run: sort --ignore-case --output contributors.yml contributors.yml\n\n - name: ๐Ÿ‘” Format\n run: pnpm format\n\n - name: ๐Ÿ’ช Commit\n run: |\n git config --local user.email \"hello@remix.run\"\n git config --local user.name \"Remix Run Bot\"\n\n git add .\n if [ -z \"$(git status --porcelain)\" ]; then\n echo \"๐Ÿ’ฟ no formatting changed\"\n exit 0\n fi\n git commit -m \"chore: format\"\n git push\n echo \"๐Ÿ’ฟ pushed formatting changes https://github.com/$GITHUB_REPOSITORY/commit/$(git rev-parse HEAD)\"\n" }, { "path": ".github/workflows/integration-full.yml", "content": "name: Branch\n\n# main/dev branches will get the full run across\n# all OS/browsers for multiple node versions\n\non:\n push:\n branches:\n - main\n - dev\n paths-ignore:\n - \".changeset/**\"\n - \"decisions/**\"\n - \"docs/**\"\n - \"examples/**\"\n - \"jest/**\"\n - \"scripts/**\"\n - \"tutorial/**\"\n - \"contributors.yml\"\n - \"**/*.md\"\n\njobs:\n build:\n name: \"โš™๏ธ Build\"\n if: github.repository == 'remix-run/react-router'\n uses: ./.github/workflows/shared-build.yml\n\n integration-ubuntu:\n name: \"๐Ÿ‘€ Integration Test\"\n if: github.repository == 'remix-run/react-router'\n uses: ./.github/workflows/shared-integration.yml\n with:\n os: \"ubuntu-latest\"\n node_version: \"[20.18, 22]\"\n browser: '[\"chromium\", \"firefox\"]'\n\n integration-windows:\n name: \"๐Ÿ‘€ Integration Test\"\n if: github.repository == 'remix-run/react-router'\n uses: ./.github/workflows/shared-integration.yml\n with:\n os: \"windows-latest\"\n node_version: \"[22]\"\n browser: '[\"msedge\"]'\n timeout: 90\n\n integration-macos:\n name: \"๐Ÿ‘€ Integration Test\"\n if: github.repository == 'remix-run/react-router'\n uses: ./.github/workflows/shared-integration.yml\n with:\n os: \"macos-latest\"\n node_version: \"[20.18, 22]\"\n browser: '[\"webkit\"]'\n" }, { "path": ".github/workflows/integration-pr-ubuntu.yml", "content": "name: PR (Base)\n\n# All PRs touching code will run tests on ubuntu/node/chromium\n\non:\n pull_request:\n paths-ignore:\n - \".changeset/**\"\n - \"decisions/**\"\n - \"docs/**\"\n - \"examples/**\"\n - \"jest/**\"\n - \"scripts/**\"\n - \"tutorial/**\"\n - \"contributors.yml\"\n - \"**/*.md\"\n\nconcurrency:\n group: ${{ github.workflow }}-${{ github.ref }}\n cancel-in-progress: true\n\njobs:\n build:\n name: \"โš™๏ธ Build\"\n if: github.repository == 'remix-run/react-router'\n uses: ./.github/workflows/shared-build.yml\n\n integration-chromium:\n name: \"๐Ÿ‘€ Integration Test\"\n if: github.repository == 'remix-run/react-router'\n uses: ./.github/workflows/shared-integration.yml\n with:\n os: \"ubuntu-latest\"\n node_version: \"[22]\"\n browser: '[\"chromium\"]'\n" }, { "path": ".github/workflows/integration-pr-windows-macos.yml", "content": "name: PR (Full)\n\n# PRs touching @react-router/dev will also run on Ubuntu/Firefox, Windows/Edge and\n# OSX/WebKit as well as an Ubuntu/Chromium run on Node 20.18.\n\non:\n pull_request:\n paths:\n - \"pnpm-lock.yaml\"\n - \"integration/**\"\n - \"packages/react-router-dev/**\"\n - \"!**/*.md\"\n\nconcurrency:\n group: ${{ github.workflow }}-${{ github.ref }}\n cancel-in-progress: true\n\njobs:\n integration-chromium:\n name: \"๐Ÿ‘€ Integration Test\"\n if: github.repository == 'remix-run/react-router'\n uses: ./.github/workflows/shared-integration.yml\n with:\n os: \"ubuntu-latest\"\n node_version: \"[20.18]\"\n browser: '[\"chromium\"]'\n\n integration-firefox:\n name: \"๐Ÿ‘€ Integration Test\"\n if: github.repository == 'remix-run/react-router'\n uses: ./.github/workflows/shared-integration.yml\n with:\n os: \"ubuntu-latest\"\n node_version: \"[22]\"\n browser: '[\"firefox\"]'\n\n integration-msedge:\n name: \"๐Ÿ‘€ Integration Test\"\n if: github.repository == 'remix-run/react-router'\n uses: ./.github/workflows/shared-integration.yml\n with:\n os: \"windows-latest\"\n node_version: \"[22]\"\n browser: '[\"msedge\"]'\n timeout: 90\n\n integration-webkit:\n name: \"๐Ÿ‘€ Integration Test\"\n if: github.repository == 'remix-run/react-router'\n uses: ./.github/workflows/shared-integration.yml\n with:\n os: \"macos-latest\"\n node_version: \"[22]\"\n browser: '[\"webkit\"]'\n" }, { "path": ".github/workflows/no-response.yml", "content": "name: ๐Ÿฅบ No Response\n\non:\n schedule:\n # Schedule for five minutes after the hour, every hour\n - cron: \"5 * * * *\"\n\npermissions:\n issues: write\n pull-requests: write\n\njobs:\n stale:\n if: github.repository == 'remix-run/react-router'\n runs-on: ubuntu-latest\n steps:\n - name: ๐Ÿฅบ Handle Ghosting\n uses: actions/stale@v10\n with:\n days-before-close: 10\n close-issue-message: >\n This issue has been automatically closed because we haven't received a\n response from the original author ๐Ÿ™ˆ. This automation helps keep the issue\n tracker clean from issues that aren't actionable. Please reach out if you\n have more information for us! ๐Ÿ™‚\n close-pr-message: >\n This PR has been automatically closed because we haven't received a\n response from the original author ๐Ÿ™ˆ. This automation helps keep the issue\n tracker clean from PRs that aren't actionable. Please reach out if you\n have more information for us! ๐Ÿ™‚\n # don't automatically mark issues/PRs as stale\n days-before-stale: -1\n stale-issue-label: needs-response\n stale-pr-label: needs-response\n" }, { "path": ".github/workflows/release-comment-manual.yml", "content": "# Used to manually trigger the release comments workflow\n\nname: ๐Ÿ’ฌ Release Comment\non:\n workflow_dispatch:\n inputs:\n dryRun:\n description: \"Should this be a dry run? (true/false)\"\n type: \"boolean\"\n required: true\n\nconcurrency:\n group: ${{ github.workflow }}-${{ github.ref }}\n cancel-in-progress: true\n\nenv:\n CI: true\n\njobs:\n comment:\n name: ๐Ÿ“ Comment on related issues and pull requests\n if: github.repository == 'remix-run/react-router'\n runs-on: ubuntu-latest\n permissions:\n issues: write # enable commenting on released issues\n pull-requests: write # enable commenting on released pull requests\n steps:\n - name: โฌ‡๏ธ Checkout repo\n uses: actions/checkout@v6\n with:\n fetch-depth: 0\n\n # IMPORTANT: if you make changes here, also make them in release.yml\n - name: ๐Ÿ“ Comment on related issues and pull requests\n uses: remix-run/release-comment-action@v0.5.1\n with:\n DRY_RUN: ${{ github.event.inputs.dryRun }}\n DIRECTORY_TO_CHECK: \"./packages\"\n PACKAGE_NAME: \"react-router\"\n ISSUE_LABELS_TO_REMOVE: \"awaiting release\"\n ISSUE_LABELS_TO_KEEP_OPEN: \"๐Ÿ—บ Roadmap\"\n" }, { "path": ".github/workflows/release.yml", "content": "# We use this singular file for all of our releases because we can only specify\n# a singular GitHub workflow file in npm's Trusted Publishing configuration.\n# See https://docs.npmjs.com/trusted-publishers for more info.\n#\n# Specific jobs only run on the proper trigger:\n#\n# - Changesets-driven pre-releases/stable releases\n# - Trigger: push to release-next/release-v6 branch\n# - jobs: release -> find_package_version -> comment\n# - Nightly releases\n# - Trigger: schedule/cron\n# - jobs: release-nightly\n# - Experimental releases (from a workflow_dispatch trigger)\n# - Trigger: workflow_dispatch\n# - jobs: release-experimental\n\nname: ๐Ÿšข Release\non:\n # Changesets-driven prereleases and stable releases\n push:\n branches:\n - \"release-next\"\n - \"release-v6\"\n # Nightly releases\n schedule:\n - cron: \"0 7 * * *\" # every day at 12AM PST\n # Experimental Releases\n workflow_dispatch:\n inputs:\n branch:\n required: true\n\nconcurrency:\n group: ${{ github.workflow }}-${{ github.ref }}\n cancel-in-progress: true\n\nenv:\n CI: true\n\njobs:\n release:\n name: ๐Ÿฆ‹ Changesets Release\n if: github.repository == 'remix-run/react-router' && github.event_name == 'push'\n runs-on: ubuntu-latest\n outputs:\n published_packages: ${{ steps.changesets.outputs.publishedPackages }}\n published: ${{ steps.changesets.outputs.published }}\n permissions:\n contents: write # enable pushing changes to the origin\n id-token: write # enable generation of an ID token for publishing\n pull-requests: write # enable opening a PR for the release\n steps:\n - name: โฌ‡๏ธ Checkout repo\n uses: actions/checkout@v6\n with:\n fetch-depth: 0\n\n - name: ๐Ÿ“ฆ Setup pnpm\n uses: pnpm/action-setup@v4\n\n - name: โŽ” Setup node\n uses: actions/setup-node@v6\n with:\n node-version: 24 # Needed for npm@11 for Trusted Publishing\n cache: \"pnpm\"\n\n - name: ๐Ÿ“ฅ Install deps\n run: pnpm install --frozen-lockfile\n\n # This action has two responsibilities. The first time the workflow runs\n # (initial push to a `release-*` branch) it will create a new branch and\n # then open a PR with the related changes for the new version. After the\n # PR is merged, the workflow will run again and this action will build +\n # publish to npm.\n - name: ๐Ÿš€ PR / Publish\n id: changesets\n # PLEASE KEEP THIS PINNED TO 1.4.10 to avoid a regression in 1.5.*\n # See https://github.com/changesets/action/issues/465\n uses: changesets/action@v1.4.10\n with:\n version: pnpm run changeset:version\n commit: \"chore: Update version for release\"\n title: \"chore: Update version for release\"\n publish: pnpm run release\n createGithubReleases: false\n env:\n GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n\n find_package_version:\n name: ๐Ÿฆ‹ Find Package\n needs: [release]\n runs-on: ubuntu-latest\n if: github.repository == 'remix-run/react-router' && github.event_name == 'push' && github.ref_name != 'release-v6' && needs.release.outputs.published == 'true'\n outputs:\n package_version: ${{ steps.find_package_version.outputs.package_version }}\n steps:\n - name: โฌ‡๏ธ Checkout repo\n uses: actions/checkout@v6\n\n - name: ๐Ÿ“ฆ Setup pnpm\n uses: pnpm/action-setup@v4\n\n - name: โŽ” Setup node\n uses: actions/setup-node@v6\n with:\n node-version: 24 # Needed for npm@11 for Trusted Publishing\n cache: \"pnpm\"\n\n - id: find_package_version\n run: |\n package_version=$(node ./scripts/find-release-from-changeset.js)\n echo \"package_version=${package_version}\" >> $GITHUB_OUTPUT\n env:\n PACKAGE_VERSION_TO_FOLLOW: \"react-router\"\n PUBLISHED_PACKAGES: ${{ needs.release.outputs.published_packages }}\n\n comment:\n name: ๐Ÿ“ Comment on related issues and pull requests\n if: github.repository == 'remix-run/react-router' && github.event_name == 'push' && github.ref_name != 'release-v6' && needs.find_package_version.outputs.package_version != ''\n needs: [release, find_package_version]\n runs-on: ubuntu-latest\n permissions:\n issues: write # enable commenting on released issues\n pull-requests: write # enable commenting on released pull requests\n steps:\n - name: โฌ‡๏ธ Checkout repo\n uses: actions/checkout@v6\n with:\n fetch-depth: 0\n\n # IMPORTANT: if you make changes here, also make them in release-comment-manual.yml\n - name: ๐Ÿ“ Comment on related issues and pull requests\n uses: remix-run/release-comment-action@v0.5.1\n with:\n DIRECTORY_TO_CHECK: \"./packages\"\n PACKAGE_NAME: \"react-router\"\n ISSUE_LABELS_TO_REMOVE: \"awaiting release\"\n ISSUE_LABELS_TO_KEEP_OPEN: \"๐Ÿ—บ Roadmap\"\n\n # HEADS UP! this \"nightly\" job will only ever run on the `main` branch due to\n # it being a cron job, and the last commit on main will be what github shows\n # as the trigger however in the checkout below we specify the `dev` branch,\n # so all the scripts in this job will be ran from that, confusing i know, so\n # in some cases we'll need to create multiple PRs when modifying nightly\n # release processes\n release-nightly:\n name: ๐ŸŒ’ Nightly Release\n if: github.repository == 'remix-run/react-router' && github.event_name == 'schedule'\n runs-on: ubuntu-latest\n permissions:\n contents: write # enable pushing changes to the origin\n id-token: write # enable generation of an ID token for publishing\n outputs:\n # will be undefined if there's no release necessary\n NEXT_VERSION: ${{ steps.version.outputs.NEXT_VERSION }}\n steps:\n - name: โฌ‡๏ธ Checkout repo\n uses: actions/checkout@v6\n with:\n ref: dev\n # checkout using a custom token so that we can push later on\n token: ${{ secrets.GITHUB_TOKEN }}\n fetch-depth: 0\n\n - name: ๐Ÿ“ฆ Setup pnpm\n uses: pnpm/action-setup@v4\n\n - name: โŽ” Setup node\n uses: actions/setup-node@v6\n with:\n node-version: 24 # Needed for npm@11 for Trusted Publishing\n cache: \"pnpm\"\n\n - name: ๐Ÿ“ฅ Install deps\n run: pnpm install --frozen-lockfile\n\n - name: ๐Ÿ•ต๏ธ Check for changes\n id: version\n run: |\n SHORT_SHA=$(git rev-parse --short HEAD)\n\n # get latest nightly tag\n LATEST_NIGHTLY_TAG=$(git tag -l v0.0.0-nightly-\\* --sort=-creatordate | head -n 1)\n\n # check if last commit to dev starts with the nightly tag we're about\n # to create (minus the date)\n # if it is, we'll skip the nightly creation\n # if not, we'll create a new nightly tag\n if [[ ${LATEST_NIGHTLY_TAG} == v0.0.0-nightly-${SHORT_SHA}-* ]]; then\n echo \"๐Ÿ›‘ Latest nightly tag is the same as the latest commit sha, skipping nightly release\"\n else\n # yyyyMMdd format (e.g. 20221207)\n DATE=$(date '+%Y%m%d')\n # v0.0.0-nightly--\n NEXT_VERSION=0.0.0-nightly-${SHORT_SHA}-${DATE}\n # set output so it can be used in other jobs\n echo \"NEXT_VERSION=${NEXT_VERSION}\" >> $GITHUB_OUTPUT\n fi\n\n - name: โคด๏ธ Update version\n if: steps.version.outputs.NEXT_VERSION\n run: |\n git config --local user.email \"hello@remix.run\"\n git config --local user.name \"Remix Run Bot\"\n git checkout -b nightly/${{ steps.version.outputs.NEXT_VERSION }}\n pnpm run version ${{steps.version.outputs.NEXT_VERSION}}\n git push origin --tags\n\n - name: ๐Ÿ— Build\n if: steps.version.outputs.NEXT_VERSION\n run: pnpm build\n\n - name: ๐Ÿš€ Publish\n if: steps.version.outputs.NEXT_VERSION\n run: pnpm run publish\n\n release-experimental:\n name: ๐Ÿงช Experimental Release\n if: github.repository == 'remix-run/react-router' && github.event_name == 'workflow_dispatch'\n runs-on: ubuntu-latest\n permissions:\n contents: write # enable pushing changes to the origin\n id-token: write # enable generation of an ID token for publishing\n steps:\n - name: โฌ‡๏ธ Checkout repo\n uses: actions/checkout@v6\n with:\n ref: ${{ github.event.inputs.branch }}\n # checkout using a custom token so that we can push later on\n token: ${{ secrets.GITHUB_TOKEN }}\n fetch-depth: 0\n\n - name: ๐Ÿ“ฆ Setup pnpm\n uses: pnpm/action-setup@v4\n\n - name: โŽ” Setup node\n uses: actions/setup-node@v6\n with:\n node-version: 24 # Needed for npm@11 for Trusted Publishing\n cache: \"pnpm\"\n\n - name: ๐Ÿ“ฅ Install deps\n run: pnpm install --frozen-lockfile\n\n - name: โคด๏ธ Update version\n run: |\n git config --local user.email \"hello@remix.run\"\n git config --local user.name \"Remix Run Bot\"\n SHORT_SHA=$(git rev-parse --short HEAD)\n NEXT_VERSION=0.0.0-experimental-${SHORT_SHA}\n git checkout -b experimental/${NEXT_VERSION}\n pnpm run version ${NEXT_VERSION}\n git push origin --tags\n\n - name: ๐Ÿ— Build\n run: pnpm build\n\n - name: ๐Ÿš€ Publish\n run: pnpm run publish\n" }, { "path": ".github/workflows/shared-build.yml", "content": "name: ๐Ÿ› ๏ธ Build\n\non:\n workflow_call:\n\nenv:\n CI: true\n\njobs:\n build:\n runs-on: ubuntu-latest\n steps:\n - name: โฌ‡๏ธ Checkout repo\n uses: actions/checkout@v6\n\n - name: ๐Ÿ“ฆ Setup pnpm\n uses: pnpm/action-setup@v4\n\n - name: โŽ” Setup node\n uses: actions/setup-node@v6\n with:\n node-version-file: \".nvmrc\"\n cache: \"pnpm\"\n\n # TODO: Track and renable once this has been fixed: https://github.com/google/wireit/issues/1297\n # - uses: google/wireit@setup-github-actions-caching/v2\n\n - name: Disable GitHub Actions Annotations\n run: |\n echo \"::remove-matcher owner=tsc::\"\n echo \"::remove-matcher owner=eslint-compact::\"\n echo \"::remove-matcher owner=eslint-stylish::\"\n\n - name: ๐Ÿ“ฅ Install deps\n run: pnpm install --frozen-lockfile\n\n - name: ๐Ÿ— Build\n run: pnpm build\n" }, { "path": ".github/workflows/shared-integration.yml", "content": "name: ๐Ÿงช Test (Integration)\n\non:\n workflow_call:\n inputs:\n os:\n required: true\n type: string\n node_version:\n required: true\n # this is limited to string | boolean | number (https://github.community/t/can-action-inputs-be-arrays/16457)\n # but we want to pass an array (node_version: \"[20, 22]\"),\n # so we'll need to manually stringify it for now\n type: string\n browser:\n required: true\n # this is limited to string | boolean | number (https://github.community/t/can-action-inputs-be-arrays/16457)\n # but we want to pass an array (browser: \"['chromium', 'firefox']\"),\n # so we'll need to manually stringify it for now\n type: string\n timeout:\n required: false\n type: number\n default: 45\n\nenv:\n CI: true\n\njobs:\n integration:\n name: \"${{ inputs.os }} / node@${{ matrix.node }} / ${{ matrix.browser }}\"\n strategy:\n fail-fast: false\n matrix:\n node: ${{ fromJSON(inputs.node_version) }}\n browser: ${{ fromJSON(inputs.browser) }}\n\n runs-on: ${{ inputs.os }}\n steps:\n - name: โฌ‡๏ธ Checkout repo\n uses: actions/checkout@v6\n\n - name: ๐Ÿ“ฆ Setup pnpm\n uses: pnpm/action-setup@v4\n\n - name: โŽ” Setup node ${{ matrix.node }}\n uses: actions/setup-node@v6\n with:\n node-version: ${{ matrix.node }}\n cache: \"pnpm\"\n\n # TODO: Track and renable once this has been fixed: https://github.com/google/wireit/issues/1297\n # - uses: google/wireit@setup-github-actions-caching/v2\n\n - name: Disable GitHub Actions Annotations\n run: |\n echo \"::remove-matcher owner=tsc::\"\n echo \"::remove-matcher owner=eslint-compact::\"\n echo \"::remove-matcher owner=eslint-stylish::\"\n\n - name: ๐Ÿ“ฅ Install deps\n run: pnpm install --frozen-lockfile\n\n - name: ๐Ÿ“ฅ Install Playwright\n run: npx playwright install --with-deps ${{ matrix.browser }}\n\n - name: ๐Ÿ‘€ Run Integration Tests ${{ matrix.browser }}\n run: \"pnpm test:integration --project=${{ matrix.browser }}\"\n timeout-minutes: ${{inputs.timeout}}\n" }, { "path": ".github/workflows/support.yml", "content": "name: \"Support Requests\"\n\non:\n issues:\n types: [labeled, unlabeled, reopened]\n\npermissions:\n issues: write\n\njobs:\n action:\n runs-on: ubuntu-latest\n steps:\n - uses: dessant/support-requests@v4\n with:\n issue-comment: >\n :wave: @{issue-author}, we use the issue tracker exclusively for bug reports\n and feature requests. However, this issue appears to be a support request.\n\n For usage questions, please use [Stack Overflow](https://stackoverflow.com/questions/tagged/react-router)\n or [Discord](https://rmx.as/discord) where there are a lot more people ready to help you out, or \n [post a new question](https://github.com/remix-run/react-router/discussions/new?category=q-a) in the \n Discussions tab of this repository.\n\n Please feel free to clarify your issue if you think it was closed prematurely.\n" }, { "path": ".github/workflows/test.yml", "content": "name: ๐Ÿงช Test\n\non:\n push:\n branches:\n - main\n - dev\n tags-ignore:\n - v*\n paths-ignore:\n - \"docs/**\"\n - \"**/README.md\"\n pull_request:\n paths-ignore:\n - \"docs/**\"\n - \"**/*.md\"\n\nconcurrency:\n group: ${{ github.workflow }}-${{ github.ref }}\n cancel-in-progress: true\n\njobs:\n test:\n name: \"๐Ÿงช Test: (Node: ${{ matrix.node }})\"\n strategy:\n fail-fast: false\n matrix:\n node:\n - 20.18\n - 22\n\n runs-on: ubuntu-latest\n\n steps:\n - name: โฌ‡๏ธ Checkout repo\n uses: actions/checkout@v6\n\n - name: ๐Ÿ“ฆ Setup pnpm\n uses: pnpm/action-setup@v4\n\n - name: โŽ” Setup node\n uses: actions/setup-node@v6\n with:\n node-version: ${{ matrix.node }}\n cache: pnpm\n check-latest: true\n\n # TODO: Track and renable once this has been fixed: https://github.com/google/wireit/issues/1297\n # - uses: google/wireit@setup-github-actions-caching/v2\n\n - name: Disable GitHub Actions Annotations\n run: |\n echo \"::remove-matcher owner=tsc::\"\n echo \"::remove-matcher owner=eslint-compact::\"\n echo \"::remove-matcher owner=eslint-stylish::\"\n\n - name: ๐Ÿ“ฅ Install deps\n run: pnpm install --frozen-lockfile\n\n - name: ๐Ÿ— Build\n run: pnpm build\n\n - name: ๐Ÿ” Typecheck\n run: pnpm typecheck\n\n - name: ๐Ÿ”ฌ Lint\n run: pnpm lint\n\n - name: ๐Ÿงช Run tests\n run: pnpm test\n" }, { "path": ".gitignore", "content": ".DS_Store\nnpm-debug.log\n\n/website/build/\nnode_modules/\n\n/examples/*/yarn.lock\n/examples/*/pnpm-lock.yaml\n/examples/*/dist\n/tutorial/dist\n/playground-local/\n/integration/playwright-report\n/integration/test-results\n\n# v5 build files\n/packages/*/cjs/\n/packages/*/esm/\n/packages/*/umd/\n\n# v6 build files\n/build/\n/packages/*/dist/\n/packages/*/LICENSE.md\n\n# v7 build files\n.react-router\n\n.wireit\n.eslintcache\n.tmp\ntsup.config.bundled_*.mjs\nbuild.utils.d.ts\nworker-configuration.d.ts\n/.env\n/NOTES.md\n\n# v7 reference docs\n/public\n" }, { "path": ".npmrc", "content": "ignore-workspace-cycles=true\nenable-pre-post-scripts=true\n" }, { "path": ".nvmrc", "content": "22" }, { "path": ".vscode/settings.json", "content": "{\n \"typescript.tsdk\": \"node_modules/typescript/lib\",\n \"typescript.enablePromptUseWorkspaceTsdk\": true\n}\n" }, { "path": "AGENTS.md", "content": "# React Router Development Guide\n\n## Commands\n\n- **Build**: `pnpm build` (all packages) or `pnpm run --filter build` (single package)\n- **Test (Jest)**: `pnpm test` (all packages), `pnpm test packages//` (single package), `pnpm test packages/react-router/__tests__/router/fetchers-test.ts` (single file), or `pnpm test -- -t \"action fetch\"` (tests matching name)\n- **Integration tests (Playwright)**: `pnpm test:integration --project chromium` (build + test all), `pnpm test:integration:run --project chromium` (test only, all), `pnpm test:integration:run --project chromium integration/middleware-test.ts` (single file), or `pnpm test:integration:run --project chromium -g \"middleware\"` (tests matching name)\n- **Typecheck**: `pnpm run typecheck`\n- **Lint**: `pnpm run lint`\n- **Docs generation**: `pnpm run docs` (regenerates API docs from JSDoc)\n- **Type generation**: `pnpm run typegen` (Framework Mode only)\n- **Clean**: `pnpm run clean` (git clean -fdX)\n\n## Modes\n\n**Five distinct modes**: Declarative, Data, Framework, RSC Data (unstable), RSC Framework (unstable). **Always identify which mode(s) a feature applies to.**\n\n1. **Declarative**: ``, ``, ``\n2. **Data**: `createBrowserRouter()` with `loader`/`action`, ``\n3. **Framework**: Vite plugin + `routes.ts` + Route Module API (route exports like `loader`, `action`, `default`) + type generation + SSR/SPA\n4. **RSC Data** (unstable): RSC runtime APIs, manual bundler setup, runtime route config\n5. **RSC Framework** (unstable): Framework Mode with `unstable_reactRouterRSC` Vite plugin\n\n**RSC mode differences:**\n\n- **RSC Framework**: `unstable_reactRouterRSC` plugin, `@vitejs/plugin-rsc`, different entry points/format\n- **RSC Data**: Manual bundler, runtime route config typically in `src/routes.ts`, `unstable_RSCRouteConfig`, different runtime APIs, `setupRscTest` in `integration/rsc/`\n\n## Architecture\n\n- **Monorepo**: pnpm workspace, packages in `packages/`\n- **Key packages**:\n - `react-router`: Core (all modes) - `lib/components.tsx`, `lib/hooks.tsx`, `lib/router/`, `lib/dom/`, `lib/rsc/`\n - `@react-router/dev`: Framework tooling - `vite/plugin.ts` (Framework), `vite/rsc/plugin.ts` (RSC Framework), `typegen/`\n - `react-router-dom`: Re-exports `react-router` (v6โ†’v7 compat)\n - `@react-router/node`, `@react-router/cloudflare`, `@react-router/express`: Server adapters\n - `@react-router/serve`: Minimal server for Framework Mode\n - `@react-router/fs-routes`: File-system routing (`flatRoutes()`)\n\n## Testing\n\n### Unit Tests (`packages/react-router/__tests__/`)\n\nUse Jest for pure routing logic, pure server runtime behavior, router state, React component behavior. No build required.\n\n```bash\npnpm test # All packages\npnpm test packages/react-router/ # Single package\npnpm test packages/react-router/__tests__/router/fetchers-test.ts # Single file\npnpm test -- -t \"action fetch\" # Tests matching name\n```\n\n### Integration Tests (`integration/`)\n\nUse Playwright for Vite plugin, build pipeline, SSR/hydration, RSC, type generation.\n\n```bash\npnpm test:integration --project chromium # Build + test all\npnpm test:integration:run --project chromium # Test only, all\npnpm test:integration:run --project chromium integration/middleware-test.ts # Single file\npnpm test:integration:run --project chromium -g \"middleware\" # Tests matching name\n```\n\n**Project**: Always use `chromium` for integration tests, unless explicitly stated otherwise.\n\n**Rebuild when**: First run, after changing `packages/` (not needed for test-only changes)\n\n**Organization**: Use `createFixture()` โ†’ `createAppFixture()` โ†’ `PlaywrightFixture`. Templates available: `vite-6-template/`, `rsc-vite-framework/`, etc. Test all applicable modes (iterate over template array when behavior should work across modes). Test both states when introducing future flags (one test with flag on, one with flag off).\n\n**RSC testing**:\n\n- **RSC Framework**: Use `createFixture` with `rsc-vite-framework/` template\n- **RSC Data**: Use `setupRscTest` in `integration/rsc/`\n\nTest shared behavior across multiple templates (e.g., `[\"vite-5-template\", \"rsc-vite-framework\"]`). Test RSC-specific features against RSC template.\n\n## routes.ts\n\nFramework Mode uses `routes.ts` in `app/`. Most tests use `flatRoutes()` for file-system routing:\n\n```ts\n// app/routes.ts\nimport { type RouteConfig } from \"@react-router/dev/routes\";\nimport { flatRoutes } from \"@react-router/fs-routes\";\n\nexport default flatRoutes() satisfies RouteConfig;\n```\n\n**File-system conventions** (`app/routes/`):\n\n- `_index.tsx` โ†’ `/` (index route)\n- `about.tsx` โ†’ `/about`\n- `blog.$slug.tsx` โ†’ `/blog/:slug` (URL param)\n- `settings.profile.tsx` โ†’ `/settings/profile` (`.` creates nesting)\n- `_layout.tsx` โ†’ pathless layout route\n\n**Manual config alternative**:\n\n```ts\nimport { index, route, layout } from \"@react-router/dev/routes\";\nexport default [\n index(\"./home.tsx\"),\n route(\"about\", \"./about.tsx\"),\n layout(\"./auth-layout.tsx\", [route(\"login\", \"./login.tsx\")]),\n];\n```\n\n## Documentation\n\n**Don't edit generated files**: `docs/api/` (from JSDoc), `.react-router/types/` (from typegen)\n\n**Mode indicators**: Every doc needs `[MODES: framework, data, declarative]`\n\n**API docs**: Edit JSDoc in `packages/react-router/lib/`, run `pnpm docs`\n\n**Unstable features**: Prefix `unstable_`, add `unstable: true` to frontmatter, include warning block\n\n## Future Flags\n\n- **Future flags** (`vX_*`): Stable breaking changes for next major\n- **Unstable flags** (`unstable_*`): Experimental, may change\n\nTest both states (on/off) for future flags. Don't break existing behavior without a flag.\n\n## Changesets\n\nWhen making changes that affect users, create a changeset at `.changeset/.md`. If iterating on a change that hasn't shipped yet, update the existing changeset file instead of creating a new one.\n\nFormat:\n\n```markdown\n---\n\"react-router\": patch\n\"@react-router/dev\": minor\n---\n\nBrief description of the change\n\n- Additional details if needed\n```\n\n## Branching\n\n- **`main`**: Latest stable release\n- **`dev`**: Active development (branch from here for code changes)\n- **`v6`**: v6.x maintenance\n- Branch from `main` for docs-only changes\n\n## Key Files\n\n| Purpose | Location |\n| ----------------- | ----------------------------------------------------------- |\n| Router | `packages/react-router/lib/router/router.ts` |\n| React API | `packages/react-router/lib/components.tsx`, `lib/hooks.tsx` |\n| Vite plugin | `packages/react-router-dev/vite/plugin.ts` |\n| RSC Vite plugin | `packages/react-router-dev/vite/rsc/plugin.ts` |\n| Type generation | `packages/react-router-dev/typegen/` |\n| Unit tests | `packages/react-router/__tests__/` |\n| Integration tests | `integration/` |\n| Decision docs | `decisions/` |\n" }, { "path": "CHANGELOG.md", "content": "\n\n# React Router Releases\n\nThis page lists all releases/release notes for React Router back to `v6.0.0`. For releases prior to v6, please refer to the [Github Releases Page](https://github.com/remix-run/react-router/releases).\n\nWe manage release notes in this file instead of the paginated Github Releases Page for 2 reasons:\n\n- Pagination in the Github UI means that you cannot easily search release notes for a large span of releases at once\n- The paginated Github interface also cuts off longer releases notes without indication in list view, and you need to click into the detail view to see the full set of release notes\n\n
\n Table of Contents\n\n- [React Router Releases](#react-router-releases)\n - [v7.13.1](#v7131)\n - [What's Changed](#whats-changed)\n - [URL Masking (unstable)](#url-masking-unstable)\n - [Patch Changes](#patch-changes)\n - [Unstable Changes](#unstable-changes)\n - [v7.13.0](#v7130)\n - [Minor Changes](#minor-changes)\n - [Patch Changes](#patch-changes-1)\n - [v7.12.0](#v7120)\n - [Security Notice](#security-notice)\n - [Minor Changes](#minor-changes-1)\n - [Patch Changes](#patch-changes-2)\n - [Unstable Changes](#unstable-changes-1)\n - [v7.11.0](#v7110)\n - [What's Changed](#whats-changed-1)\n - [`vite preview` Support](#vite-preview-support)\n - [Stabilized Client-side `onError`](#stabilized-client-side-onerror)\n - [Call-site Revalidation Opt-out (unstable)](#call-site-revalidation-opt-out-unstable)\n - [Minor Changes](#minor-changes-2)\n - [Patch Changes](#patch-changes-3)\n - [Unstable Changes](#unstable-changes-2)\n - [v7.10.1](#v7101)\n - [Patch Changes](#patch-changes-4)\n - [v7.10.0](#v7100)\n - [What's Changed](#whats-changed-2)\n - [Stabilized `future.v8_splitRouteModules`](#stabilized-futurev8_splitroutemodules)\n - [Stabilized `future.v8_viteEnvironmentApi`](#stabilized-futurev8_viteenvironmentapi)\n - [Stabilized `fetcher.reset()`](#stabilized-fetcherreset)\n - [Stabilized `DataStrategyMatch.shouldCallHandler()`](#stabilized-datastrategymatchshouldcallhandler)\n - [Minor Changes](#minor-changes-3)\n - [Patch Changes](#patch-changes-5)\n - [Unstable Changes](#unstable-changes-3)\n - [v7.9.6](#v796)\n - [Security Notice](#security-notice-1)\n - [Patch Changes](#patch-changes-6)\n - [Unstable Changes](#unstable-changes-4)\n - [v7.9.5](#v795)\n - [What's Changed](#whats-changed-3)\n - [Instrumentation (unstable)](#instrumentation-unstable)\n - [Patch Changes](#patch-changes-7)\n - [Unstable Changes](#unstable-changes-5)\n - [v7.9.4](#v794)\n - [Security Notice](#security-notice-2)\n - [What's Changed](#whats-changed-4)\n - [`useRoute()` (unstable)](#useroute-unstable)\n - [Patch Changes](#patch-changes-8)\n - [Unstable Changes](#unstable-changes-6)\n - [v7.9.3](#v793)\n - [Patch Changes](#patch-changes-9)\n - [v7.9.2](#v792)\n - [What's Changed](#whats-changed-5)\n - [RSC Framework Mode (unstable)](#rsc-framework-mode-unstable)\n - [Fetcher Reset (unstable)](#fetcher-reset-unstable)\n - [Patch Changes](#patch-changes-10)\n - [Unstable Changes](#unstable-changes-7)\n - [v7.9.1](#v791)\n - [Patch Changes](#patch-changes-11)\n - [v7.9.0](#v790)\n - [Security Notice](#security-notice-3)\n - [What's Changed](#whats-changed-6)\n - [Stable Middleware and Context APIs](#stable-middleware-and-context-apis)\n - [Minor Changes](#minor-changes-4)\n - [Patch Changes](#patch-changes-12)\n - [Unstable Changes](#unstable-changes-8)\n - [v7.8.2](#v782)\n - [Patch Changes](#patch-changes-13)\n - [Unstable Changes](#unstable-changes-9)\n - [v7.8.1](#v781)\n - [Patch Changes](#patch-changes-14)\n - [Unstable Changes](#unstable-changes-10)\n - [v7.8.0](#v780)\n - [What's Changed](#whats-changed-7)\n - [Consistently named `loaderData` values](#consistently-named-loaderdata-values)\n - [Improvements/fixes to the middleware APIs (unstable)](#improvementsfixes-to-the-middleware-apis-unstable)\n - [Minor Changes](#minor-changes-5)\n - [Patch Changes](#patch-changes-15)\n - [Unstable Changes](#unstable-changes-11)\n - [Changes by Package](#changes-by-package)\n - [v7.7.1](#v771)\n - [Patch Changes](#patch-changes-16)\n - [Unstable Changes](#unstable-changes-12)\n - [v7.7.0](#v770)\n - [What's Changed](#whats-changed-8)\n - [Unstable RSC APIs](#unstable-rsc-apis)\n - [Minor Changes](#minor-changes-6)\n - [Patch Changes](#patch-changes-17)\n - [Unstable Changes](#unstable-changes-13)\n - [Changes by Package](#changes-by-package-1)\n - [v7.6.3](#v763)\n - [Patch Changes](#patch-changes-18)\n - [v7.6.2](#v762)\n - [Patch Changes](#patch-changes-19)\n - [v7.6.1](#v761)\n - [Patch Changes](#patch-changes-20)\n - [Unstable Changes](#unstable-changes-14)\n - [v7.6.0](#v760)\n - [What's Changed](#whats-changed-9)\n - [`routeDiscovery` Config Option](#routediscovery-config-option)\n - [Automatic Types for Future Flags](#automatic-types-for-future-flags)\n - [Minor Changes](#minor-changes-7)\n - [Patch Changes](#patch-changes-21)\n - [Unstable Changes](#unstable-changes-15)\n - [Changes by Package](#changes-by-package-2)\n - [v7.5.3](#v753)\n - [Patch Changes](#patch-changes-22)\n - [v7.5.2](#v752)\n - [Security Notice](#security-notice-4)\n - [Patch Changes](#patch-changes-23)\n - [v7.5.1](#v751)\n - [Patch Changes](#patch-changes-24)\n - [Unstable Changes](#unstable-changes-16)\n - [v7.5.0](#v750)\n - [What's Changed](#whats-changed-10)\n - [`route.lazy` Object API](#routelazy-object-api)\n - [Minor Changes](#minor-changes-8)\n - [Patch Changes](#patch-changes-25)\n - [Unstable Changes](#unstable-changes-17)\n - [Changes by Package](#changes-by-package-3)\n - [v7.4.1](#v741)\n - [Security Notice](#security-notice-5)\n - [Patch Changes](#patch-changes-26)\n - [Unstable Changes](#unstable-changes-18)\n - [v7.4.0](#v740)\n - [Minor Changes](#minor-changes-9)\n - [Patch Changes](#patch-changes-27)\n - [Unstable Changes](#unstable-changes-19)\n - [Changes by Package](#changes-by-package-4)\n - [v7.3.0](#v730)\n - [Minor Changes](#minor-changes-10)\n - [Patch Changes](#patch-changes-28)\n - [Unstable Changes](#unstable-changes-20)\n - [Client-side `context` (unstable)](#client-side-context-unstable)\n - [Middleware (unstable)](#middleware-unstable)\n - [Middleware `context` parameter](#middleware-context-parameter)\n - [`unstable_SerializesTo`](#unstable_serializesto)\n - [Changes by Package](#changes-by-package-5)\n - [v7.2.0](#v720)\n - [What's Changed](#whats-changed-11)\n - [Type-safe `href` utility](#type-safe-href-utility)\n - [Prerendering with a SPA Fallback](#prerendering-with-a-spa-fallback)\n - [Allow a root `loader` in SPA Mode](#allow-a-root-loader-in-spa-mode)\n - [Minor Changes](#minor-changes-11)\n - [Patch Changes](#patch-changes-29)\n - [Unstable Changes](#unstable-changes-21)\n - [Split Route Modules (unstable)](#split-route-modules-unstable)\n - [Changes by Package](#changes-by-package-6)\n - [v7.1.5](#v715)\n - [Patch Changes](#patch-changes-30)\n - [v7.1.4](#v714)\n - [Patch Changes](#patch-changes-31)\n - [v7.1.3](#v713)\n - [Patch Changes](#patch-changes-32)\n - [v7.1.2](#v712)\n - [Patch Changes](#patch-changes-33)\n - [v7.1.1](#v711)\n - [Patch Changes](#patch-changes-34)\n - [v7.1.0](#v710)\n - [Minor Changes](#minor-changes-12)\n - [Patch Changes](#patch-changes-35)\n - [Changes by Package](#changes-by-package-7)\n - [v7.0.2](#v702)\n - [Patch Changes](#patch-changes-36)\n - [v7.0.1](#v701)\n - [Patch Changes](#patch-changes-37)\n - [v7.0.0](#v700)\n - [Breaking Changes](#breaking-changes)\n - [Package Restructuring](#package-restructuring)\n - [Removed Adapter Re-exports](#removed-adapter-re-exports)\n - [Removed APIs](#removed-apis)\n - [Minimum Versions](#minimum-versions)\n - [Adopted Future Flag Behaviors](#adopted-future-flag-behaviors)\n - [Vite Compiler](#vite-compiler)\n - [Exposed Router Promises](#exposed-router-promises)\n - [Other Notable Changes](#other-notable-changes)\n - [`routes.ts`](#routests)\n - [Type-safety improvements](#type-safety-improvements)\n - [Prerendering](#prerendering)\n - [Major Changes (`react-router`)](#major-changes-react-router)\n - [Major Changes (`@react-router/*`)](#major-changes-react-router-1)\n - [Minor Changes](#minor-changes-13)\n - [Patch Changes](#patch-changes-38)\n - [Changes by Package](#changes-by-package-8)\n- [React Router v6 Releases](#react-router-v6-releases)\n - [v6.30.3](#v6303)\n - [Security Notice](#security-notice-6)\n - [Patch Changes](#patch-changes-39)\n - [v6.30.2](#v6302)\n - [Security Notice](#security-notice-7)\n - [Patch Changes](#patch-changes-40)\n - [v6.30.1](#v6301)\n - [Patch Changes](#patch-changes-41)\n - [v6.30.0](#v6300)\n - [Minor Changes](#minor-changes-14)\n - [Patch Changes](#patch-changes-42)\n - [v6.29.0](#v6290)\n - [Minor Changes](#minor-changes-15)\n - [Patch Changes](#patch-changes-43)\n - [v6.28.2](#v6282)\n - [Patch Changes](#patch-changes-44)\n - [v6.28.1](#v6281)\n - [Patch Changes](#patch-changes-45)\n - [v6.28.0](#v6280)\n - [What's Changed](#whats-changed-12)\n - [Minor Changes](#minor-changes-16)\n - [Patch Changes](#patch-changes-46)\n - [v6.27.0](#v6270)\n - [What's Changed](#whats-changed-13)\n - [Stabilized APIs](#stabilized-apis)\n - [Minor Changes](#minor-changes-17)\n - [Patch Changes](#patch-changes-47)\n - [v6.26.2](#v6262)\n - [Patch Changes](#patch-changes-48)\n - [v6.26.1](#v6261)\n - [Patch Changes](#patch-changes-49)\n - [v6.26.0](#v6260)\n - [Minor Changes](#minor-changes-18)\n - [Patch Changes](#patch-changes-50)\n - [v6.25.1](#v6251)\n - [Patch Changes](#patch-changes-51)\n - [v6.25.0](#v6250)\n - [What's Changed](#whats-changed-14)\n - [Stabilized `v7_skipActionErrorRevalidation`](#stabilized-v7_skipactionerrorrevalidation)\n - [Minor Changes](#minor-changes-19)\n - [Patch Changes](#patch-changes-52)\n - [v6.24.1](#v6241)\n - [Patch Changes](#patch-changes-53)\n - [v6.24.0](#v6240)\n - [What's Changed](#whats-changed-15)\n - [Lazy Route Discovery (a.k.a. \"Fog of War\")](#lazy-route-discovery-aka-fog-of-war)\n - [Minor Changes](#minor-changes-20)\n - [Patch Changes](#patch-changes-54)\n - [v6.23.1](#v6231)\n - [Patch Changes](#patch-changes-55)\n - [v6.23.0](#v6230)\n - [What's Changed](#whats-changed-16)\n - [Data Strategy (unstable)](#data-strategy-unstable)\n - [Skip Action Error Revalidation (unstable)](#skip-action-error-revalidation-unstable)\n - [Minor Changes](#minor-changes-21)\n - [v6.22.3](#v6223)\n - [Patch Changes](#patch-changes-56)\n - [v6.22.2](#v6222)\n - [Patch Changes](#patch-changes-57)\n - [v6.22.1](#v6221)\n - [Patch Changes](#patch-changes-58)\n - [v6.22.0](#v6220)\n - [What's Changed](#whats-changed-17)\n - [Core Web Vitals Technology Report Flag](#core-web-vitals-technology-report-flag)\n - [Minor Changes](#minor-changes-22)\n - [Patch Changes](#patch-changes-59)\n - [v6.21.3](#v6213)\n - [Patch Changes](#patch-changes-60)\n - [v6.21.2](#v6212)\n - [Patch Changes](#patch-changes-61)\n - [v6.21.1](#v6211)\n - [Patch Changes](#patch-changes-62)\n - [v6.21.0](#v6210)\n - [What's Changed](#whats-changed-18)\n - [`future.v7_relativeSplatPath`](#futurev7_relativesplatpath)\n - [Partial Hydration](#partial-hydration)\n - [Minor Changes](#minor-changes-23)\n - [Patch Changes](#patch-changes-63)\n - [v6.20.1](#v6201)\n - [Patch Changes](#patch-changes-64)\n - [v6.20.0](#v6200)\n - [Minor Changes](#minor-changes-24)\n - [Patch Changes](#patch-changes-65)\n - [v6.19.0](#v6190)\n - [What's Changed](#whats-changed-19)\n - [`unstable_flushSync` API](#unstable_flushsync-api)\n - [Minor Changes](#minor-changes-25)\n - [Patch Changes](#patch-changes-66)\n - [v6.18.0](#v6180)\n - [What's Changed](#whats-changed-20)\n - [New Fetcher APIs](#new-fetcher-apis)\n - [Persistence Future Flag (`future.v7_fetcherPersist`)](#persistence-future-flag-futurev7_fetcherpersist)\n - [Minor Changes](#minor-changes-26)\n - [Patch Changes](#patch-changes-67)\n - [v6.17.0](#v6170)\n - [What's Changed](#whats-changed-21)\n - [View Transitions ๐Ÿš€](#view-transitions-)\n - [Minor Changes](#minor-changes-27)\n - [Patch Changes](#patch-changes-68)\n - [v6.16.0](#v6160)\n - [Minor Changes](#minor-changes-28)\n - [Patch Changes](#patch-changes-69)\n - [v6.15.0](#v6150)\n - [Minor Changes](#minor-changes-29)\n - [Patch Changes](#patch-changes-70)\n - [v6.14.2](#v6142)\n - [Patch Changes](#patch-changes-71)\n - [v6.14.1](#v6141)\n - [Patch Changes](#patch-changes-72)\n - [v6.14.0](#v6140)\n - [What's Changed](#whats-changed-22)\n - [JSON/Text Submissions](#jsontext-submissions)\n - [Minor Changes](#minor-changes-30)\n - [Patch Changes](#patch-changes-73)\n - [v6.13.0](#v6130)\n - [What's Changed](#whats-changed-23)\n - [`future.v7_startTransition`](#futurev7_starttransition)\n - [Minor Changes](#minor-changes-31)\n - [Patch Changes](#patch-changes-74)\n - [v6.12.1](#v6121)\n - [Patch Changes](#patch-changes-75)\n - [v6.12.0](#v6120)\n - [What's Changed](#whats-changed-24)\n - [`React.startTransition` support](#reactstarttransition-support)\n - [Minor Changes](#minor-changes-32)\n - [Patch Changes](#patch-changes-76)\n - [v6.11.2](#v6112)\n - [Patch Changes](#patch-changes-77)\n - [v6.11.1](#v6111)\n - [Patch Changes](#patch-changes-78)\n - [v6.11.0](#v6110)\n - [Minor Changes](#minor-changes-33)\n - [Patch Changes](#patch-changes-79)\n - [v6.10.0](#v6100)\n - [What's Changed](#whats-changed-25)\n - [Minor Changes](#minor-changes-34)\n - [`future.v7_normalizeFormMethod`](#futurev7_normalizeformmethod)\n - [Patch Changes](#patch-changes-80)\n - [v6.9.0](#v690)\n - [What's Changed](#whats-changed-26)\n - [`Component`/`ErrorBoundary` route properties](#componenterrorboundary-route-properties)\n - [Introducing Lazy Route Modules](#introducing-lazy-route-modules)\n - [Minor Changes](#minor-changes-35)\n - [Patch Changes](#patch-changes-81)\n - [v6.8.2](#v682)\n - [Patch Changes](#patch-changes-82)\n - [v6.8.1](#v681)\n - [Patch Changes](#patch-changes-83)\n - [v6.8.0](#v680)\n - [Minor Changes](#minor-changes-36)\n - [Patch Changes](#patch-changes-84)\n - [v6.7.0](#v670)\n - [Minor Changes](#minor-changes-37)\n - [Patch Changes](#patch-changes-85)\n - [v6.6.2](#v662)\n - [Patch Changes](#patch-changes-86)\n - [v6.6.1](#v661)\n - [Patch Changes](#patch-changes-87)\n - [v6.6.0](#v660)\n - [What's Changed](#whats-changed-27)\n - [Minor Changes](#minor-changes-38)\n - [Patch Changes](#patch-changes-88)\n - [v6.5.0](#v650)\n - [What's Changed](#whats-changed-28)\n - [Minor Changes](#minor-changes-39)\n - [Patch Changes](#patch-changes-89)\n - [v6.4.5](#v645)\n - [Patch Changes](#patch-changes-90)\n - [v6.4.4](#v644)\n - [Patch Changes](#patch-changes-91)\n - [v6.4.3](#v643)\n - [Patch Changes](#patch-changes-92)\n - [v6.4.2](#v642)\n - [Patch Changes](#patch-changes-93)\n - [v6.4.1](#v641)\n - [Patch Changes](#patch-changes-94)\n - [v6.4.0](#v640)\n - [What's Changed](#whats-changed-29)\n - [Remix Data APIs](#remix-data-apis)\n - [Patch Changes](#patch-changes-95)\n - [v6.3.0](#v630)\n - [Minor Changes](#minor-changes-40)\n - [v6.2.2](#v622)\n - [Patch Changes](#patch-changes-96)\n - [v6.2.1](#v621)\n - [Patch Changes](#patch-changes-97)\n - [v6.2.0](#v620)\n - [Minor Changes](#minor-changes-41)\n - [Patch Changes](#patch-changes-98)\n - [v6.1.1](#v611)\n - [Patch Changes](#patch-changes-99)\n - [v6.1.0](#v610)\n - [Minor Changes](#minor-changes-42)\n - [Patch Changes](#patch-changes-100)\n - [v6.0.2](#v602)\n - [Patch Changes](#patch-changes-101)\n - [v6.0.1](#v601)\n - [Patch Changes](#patch-changes-102)\n - [v6.0.0](#v600)\n\n
\n\n\n\n## v7.13.1\n\nDate: 2026-02-23\n\n## What's Changed\n\n### URL Masking (unstable)\n\nThis release includes a new `` API which brings first-class support for URL masking to Framework/Data Mode ([RFC](https://github.com/remix-run/react-router/discussions/9864)). This allows the same type of UI you could achieve in Declarative Mode via [manual `backgroundLocation` management](https://github.com/remix-run/react-router/tree/main/examples/modal). That example has been converted to Data Mode using the new API [here](https://github.com/remix-run/react-router/tree/main/examples/modal-data-router).\n\n### Patch Changes\n\n- `react-router` - Clear timeout when `turbo-stream` encoding completes ([#14810](https://github.com/remix-run/react-router/pull/14810))\n- `react-router` - Improve error message when `Origin` header is invalid ([#14743](https://github.com/remix-run/react-router/pull/14743))\n- `react-router` - Fix `matchPath` optional params matching without a `\"/\"` separator. ([#14689](https://github.com/remix-run/react-router/pull/14689))\n - `matchPath(\"/users/:id?\", \"/usersblah\")` now returns null\n - `matchPath(\"/test_route/:part?\", \"/test_route_more\")` now returns null.\n- `react-router` - Fix `HydrateFallback` rendering during initial lazy route discovery with matching splat route ([#14740](https://github.com/remix-run/react-router/pull/14740))\n- `react-router` - Preserve query parameters and hash on manifest version mismatch reload ([#14813](https://github.com/remix-run/react-router/pull/14813))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `react-router` - RSC: fix null reference exception in bad codepath leading to invalid route tree comparisons ([#14780](https://github.com/remix-run/react-router/pull/14780))\n- `react-router` - RSC: add `unstable_getRequest` API ([#14758](https://github.com/remix-run/react-router/pull/14758))\n- `react-router` - RSC: Update failed origin checks to return a 400 status and appropriate UI instead of a generic 500 ([#14755](https://github.com/remix-run/react-router/pull/14755))\n- `react-router` - Add support for `` in Framework/Data Mode which allows users to navigate to a URL in the router but \"mask\" the URL displayed in the browser ([#14716](https://github.com/remix-run/react-router/pull/14716))\n - This is useful for contextual routing usages such as displaying an image in a modal on top of a gallery, but displaying a browser URL directly to the image that can be shared and loaded without the contextual gallery in the background\n - The masked location, if present, will be available on `useLocation().unstable_mask` so you can detect whether you are currently masked or not\n - Masked URLs only work for SPA use cases, and will be removed from `history.state` during SSR\n - This provides a first-class API to mask URLs in Framework/Data Mode to achieve the same behavior you could do in Declarative Mode via [manual `backgroundLocation` management](https://github.com/remix-run/react-router/tree/main/examples/modal).\n\n ```tsx\n // routes/gallery.tsx\n export function clientLoader({ request }: Route.LoaderArgs) {\n let sp = new URL(request.url).searchParams;\n return {\n images: getImages(),\n // When the router location has the image param, load the modal data\n modalImage: sp.has(\"image\") ? getImage(sp.get(\"image\")!) : null,\n };\n }\n\n export default function Gallery({ loaderData }: Route.ComponentProps) {\n return (\n <>\n \n {loaderData.images.map((image) => (\n \n {image.alt}\n \n ))}\n \n\n {/* When the modal data exists, display the modal */}\n {data.modalImage ? (\n \n {data.modalImage.alt}\n \n ) : null}\n \n );\n }\n ```\n\n**Full Changelog**: [`v7.13.0...v7.13.1`](https://github.com/remix-run/react-router/compare/react-router@7.13.0...react-router@7.13.1)\n\n## v7.13.0\n\nDate: 2026-01-23\n\n### Minor Changes\n\n- `react-router` - Add `crossOrigin` prop to `Links` component ([#14687](https://github.com/remix-run/react-router/pull/14687))\n\n### Patch Changes\n\n- `react-router` - Fix double slash normalization for `useNavigate` paths with a colon ([#14718](https://github.com/remix-run/react-router/pull/14718))\n- `react-router` - Fix missing `nonce` on inline `criticalCss` ([#14691](https://github.com/remix-run/react-router/pull/14691))\n- `react-router` - Update failed origin checks to return a 400 status instead of a 500 ([#14737](https://github.com/remix-run/react-router/pull/14737))\n- `react-router` - Loosen `allowedActionOrigins` glob check so `**` matches all domains ([#14722](https://github.com/remix-run/react-router/pull/14722))\n- `@react-router/dev` - Bump `@remix-run/node-fetch-server` dep ([#14704](https://github.com/remix-run/react-router/pull/14704))\n- `@react-router/fs-routes` - Fix route file paths when routes directory is outside of the app directory ([#13937](https://github.com/remix-run/react-router/pull/13937))\n\n**Full Changelog**: [`v7.12.0...v7.13.0`](https://github.com/remix-run/react-router/compare/react-router@7.12.0...react-router@7.13.0)\n\n## v7.12.0\n\nDate: 2026-01-07\n\n### Security Notice\n\nThis release addresses 3 security vulnerabilities:\n\n- [CSRF in React Router Action/Server Action Request Processing](https://github.com/remix-run/react-router/security/advisories/GHSA-h5cw-625j-3rxh)\n- [XSS via Open Redirects](https://github.com/remix-run/react-router/security/advisories/GHSA-2w69-qvjg-hvjx)\n- [React Router SSR XSS in ScrollRestoration](https://github.com/remix-run/react-router/security/advisories/GHSA-8v8x-cx79-35w7)\n\n### Minor Changes\n\n- `react-router` - Add additional layer of CSRF protection by rejecting submissions to UI routes from external origins ([#14708](https://github.com/remix-run/react-router/pull/14708))\n - If you need to permit access to specific external origins, there is a new `allowedActionOrigins` config field in `react-router.config.ts` where you can specify external origins\n\n### Patch Changes\n\n- `react-router` - Fix `generatePath` when used with suffixed params (i.e., `/books/:id.json`) ([#14269](https://github.com/remix-run/react-router/pull/14269))\n- `react-router` - Escape HTML in scroll restoration keys ([#14705](https://github.com/remix-run/react-router/pull/14705))\n- `react-router` - Validate redirect locations ([#14706](https://github.com/remix-run/react-router/pull/14706))\n- `@react-router/dev` - Fix `Maximum call stack size exceeded` errors when HMR is triggered against code with cyclic imports ([#14522](https://github.com/remix-run/react-router/pull/14522))\n- `@react-router/dev` - Skip SSR middleware in `vite preview` server for SPA mode ([#14673](https://github.com/remix-run/react-router/pull/14673))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `react-router` - Preserve `clientLoader.hydrate=true` when using `` ([#14674](https://github.com/remix-run/react-router/pull/14674))\n- `react-router` - Pass `` value through to the underlying `importmap` `script` tag when using `future.unstable_subResourceIntegrity` ([#14675](https://github.com/remix-run/react-router/pull/14675))\n- `react-router` - Export `UNSAFE_createMemoryHistory` and `UNSAFE_createHashHistory` alongside `UNSAFE_createBrowserHistory` for consistency ([#14663](https://github.com/remix-run/react-router/pull/14663))\n - These are not intended to be used for new apps but intended to help apps using `unstable_HistoryRouter` migrate from v6->v7 so they can adopt the newer APIs\n- `@react-router/dev` - Add a new `future.unstable_trailingSlashAwareDataRequests` flag to provide consistent behavior of `request.pathname` inside `middleware`, `loader`, and `action` functions on document and data requests when a trailing slash is present in the browser URL. ([#14644](https://github.com/remix-run/react-router/pull/14644))\n - Currently, your HTTP and `request` pathnames would be as follows for `/a/b/c` and `/a/b/c/`\n\n | URL `/a/b/c` | **HTTP pathname** | **`request` pathname`** |\n | ------------ | ----------------- | ----------------------- |\n | **Document** | `/a/b/c` | `/a/b/c` โœ… |\n | **Data** | `/a/b/c.data` | `/a/b/c` โœ… |\n\n | URL `/a/b/c/` | **HTTP pathname** | **`request` pathname`** |\n | ------------- | ----------------- | ----------------------- |\n | **Document** | `/a/b/c/` | `/a/b/c/` โœ… |\n | **Data** | `/a/b/c.data` | `/a/b/c` โš ๏ธ |\n\n - With this flag enabled, these pathnames will be made consistent though a new `_.data` format for client-side `.data` requests:\n\n | URL `/a/b/c` | **HTTP pathname** | **`request` pathname`** |\n | ------------ | ----------------- | ----------------------- |\n | **Document** | `/a/b/c` | `/a/b/c` โœ… |\n | **Data** | `/a/b/c.data` | `/a/b/c` โœ… |\n\n | URL `/a/b/c/` | **HTTP pathname** | **`request` pathname`** |\n | ------------- | ------------------ | ----------------------- |\n | **Document** | `/a/b/c/` | `/a/b/c/` โœ… |\n | **Data** | `/a/b/c/_.data` โฌ…๏ธ | `/a/b/c/` โœ… |\n\n - This a bug fix but we are putting it behind an opt-in flag because it has the potential to be a \"breaking bug fix\" if you are relying on the URL format for any other application or caching logic\n - Enabling this flag also changes the format of client side `.data` requests from `/_root.data` to `/_.data` when navigating to `/` to align with the new format - This does not impact the `request` pathname which is still `/` in all cases\n\n**Full Changelog**: [`v7.11.0...v7.12.0`](https://github.com/remix-run/react-router/compare/react-router@7.11.0...react-router@7.12.0)\n\n## v7.11.0\n\nDate: 2025-12-17\n\n### What's Changed\n\nWe've added `vite preview` support and stabilized the client-side `onError` API - please make the appropriate changes if you've adopted the `unstable_onError` API already in a prior release.\n\n#### `vite preview` Support\n\nWe've added support for [`vite preview`](https://vite.dev/guide/cli#vite-preview) when using Framework mode to make it easy to preview your production build.\n\n#### Stabilized Client-side `onError`\n\nThe existing ``/`` APIs have been stabilized as ``/``. Please see the [Error Reporting](https://reactrouter.com/7.11.0/how-to/error-reporting#client-errors) docs for more information.\n\n#### Call-site Revalidation Opt-out (unstable)\n\nWe've added initial unstable support for call-site revalidation opt-out via a new `unstable_defaultShouldRevalidate` flag ([RFC](https://github.com/remix-run/react-router/discussions/10006)). This flag is available on all navigation/fetcher submission APIs to alter standard revalidation behavior. If any routes include a `shouldRevalidate` function, then the flag value will be passed to that function so the route has the final say on revalidation behavior.\n\n```tsx\n
\nsubmit(data, { method: \"post\", unstable_defaultShouldRevalidate: false })\n\nfetcher.submit(data, { method: \"post\", unstable_defaultShouldRevalidate: false })\n```\n\nThis flag is also available on non-submission navigational use cases - for example, you may want to opt-out of revalidation when adding a search param that doesn't impact the UI:\n\n```tsx\n;\nnavigate(\"?analytics-param=1\", { unstable_defaultShouldRevalidate: false });\nsetSearchParams(params, { unstable_defaultShouldRevalidate: false });\n```\n\n### Minor Changes\n\n- `react-router` - Stabilize ``/`` ([#14546](https://github.com/remix-run/react-router/pull/14546))\n- `@react-router/dev` - Add `vite preview` support ([#14507](https://github.com/remix-run/react-router/pull/14507))\n\n### Patch Changes\n\n- `react-router` - Fix `unstable_useTransitions` prop on `` component to permit omission for backwards compatibility ([#14646](https://github.com/remix-run/react-router/pull/14646))\n- `react-router` - Allow redirects to be returned from client side middleware ([#14598](https://github.com/remix-run/react-router/pull/14598))\n- `react-router` - Handle `dataStrategy` implementations that return insufficient result sets by adding errors for routes without any available result ([#14627](https://github.com/remix-run/react-router/pull/14627))\n- `@react-router/serve` - Update `compression` and `morgan` dependencies to address `on-headers` CVE: [GHSA-76c9-3jph-rj3q](https://github.com/advisories/GHSA-76c9-3jph-rj3q) ([#14652](https://github.com/remix-run/react-router/pull/14652))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `react-router` - RSC: Support for throwing `data()` and Response from server component render phase ([#14632](https://github.com/remix-run/react-router/pull/14632))\n - Response body is not serialized as async work is not allowed as error encoding phase.\n - If you wish to transmit data to the boundary, throw `data()` instead\n- `react-router` - RSC: Support for throwing `redirect` Response's at render time ([#14596](https://github.com/remix-run/react-router/pull/14596))\n- `react-router` - RSC: `routeRSCServerRequest` replace `fetchServer` with `serverResponse` ([#14597](https://github.com/remix-run/react-router/pull/14597))\n- `@react-router/dev` - RSC (Framework mode): Manual chunking for `react` and `react-router` deps ([#14655](https://github.com/remix-run/react-router/pull/14655))\n- `@react-router/dev` - RSC (Framework mode): Optimize `react-server-dom-webpack` if in project `package.json` ([#14656](https://github.com/remix-run/react-router/pull/14656))\n- `@react-router/{dev,serve}` - RSC (Framework mode): Support custom entrypoints ([#14643](https://github.com/remix-run/react-router/pull/14643))\n- `react-router` - Add a new `unstable_defaultShouldRevalidate` flag to various APIs to allow opt-ing out of standard revalidation behaviors ([#14542](https://github.com/remix-run/react-router/pull/14542))\n\n**Full Changelog**: [`v7.10.1...v7.11.0`](https://github.com/remix-run/react-router/compare/react-router@7.10.1...react-router@7.11.0)\n\n## v7.10.1\n\nDate: 2025-12-04\n\n### Patch Changes\n\n- `react-router` - Update the `useOptimistic` stub we provide for React 18 users to use a stable setter function to avoid potential `useEffect` loops - specifically when using `` ([#14628](https://github.com/remix-run/react-router/pull/14628))\n- `@react-router/dev` - Import ESM package `pkg-types` with a dynamic `import()` to fix issues on Node 20.18 ([#14624](https://github.com/remix-run/react-router/pull/14624))\n- `@react-router/dev` - Update `valibot` dependency to `^1.2.0` to address [GHSA-vqpr-j7v3-hqw9](https://github.com/advisories/GHSA-vqpr-j7v3-hqw9) ([#14608](https://github.com/remix-run/react-router/pull/14608))\n\n**Full Changelog**: [`v7.10.0...v7.10.1`](https://github.com/remix-run/react-router/compare/react-router@7.10.0...react-router@7.10.1)\n\n## v7.10.0\n\nDate: 2025-12-02\n\n### What's Changed\n\nWe've stabilized a handful of existing APIs and future flags in this release, please make the appropriate changes if you'd adopted any of these APIs in their unstable state!\n\n#### Stabilized `future.v8_splitRouteModules`\n\nThe existing `future.unstable_splitRouteModules` flag has been stabilized as `future.v8_splitRouteModules` in `react-router.config.ts`. Please see the [docs](https://reactrouter.com/7.10.0/upgrading/future#futurev8_splitroutemodules) for more information on adopting this flag.\n\n#### Stabilized `future.v8_viteEnvironmentApi`\n\nThe existing `future.unstable_viteEnvironmentApi` flag has been stabilized as `future.v8_viteEnvironmentApi` in `react-router.config.ts`. Please see the [docs](https://reactrouter.com/7.10.0/upgrading/future#futurev8_viteenvironmentapi) for more information on adopting this flag.\n\n#### Stabilized `fetcher.reset()`\n\nThe existing `fetcher.unstable_reset()` API has been stabilized as `fetcher.reset()`.\n\n#### Stabilized `DataStrategyMatch.shouldCallHandler()`\n\nThe existing low-level `DataStrategyMatch.unstable_shouldCallHandler()`/`DataStrategyMatch.unstable_shouldRevalidateArgs` APIs have been stabilized as `DataStrategyMatch.shouldCallHandler()`/`DataStrategyMatch.shouldRevalidateArgs`. Please see the [docs](https://reactrouter.com/7.10.0/how-to/data-strategy) for information about using a custom `dataStrategy` and how to migrate away from the deprecated `DataStrategyMatch.shouldLoad` API if you are using that today.\n\n### Minor Changes\n\n- `react-router` - Stabilize `fetcher.reset()` ([#14545](https://github.com/remix-run/react-router/pull/14545))\n - โš ๏ธ This is a breaking change if you have begun using `fetcher.unstable_reset()` - please update your code to use `fetcher.reset()`\n- `react-router` - Stabilize the `dataStrategy` `match.shouldCallHandler()`/`match.shouldRevalidateArgs` APIs ([#14592](https://github.com/remix-run/react-router/pull/14592))\n - The `match.shouldLoad` API is now marked deprecated in favor of these more powerful alternatives\n - โš ๏ธ This is a breaking change if you have begun using `match.unstable_shouldCallHandler()`/`match.unstable_shouldRevalidateArgs` - please update your code to use `match.shouldCallHandler()`/`match.shouldRevalidateArgs`\n- `@react-router/dev` - Stabilize `future.v8_splitRouteModules`, replacing `future.unstable_splitRouteModules` ([#14595](https://github.com/remix-run/react-router/pull/14595))\n - โš ๏ธ This is a breaking change if you have begun using `future.unstable_splitRouteModules` - please update your `react-router.config.ts`\n- `@react-router/dev` - Stabilize `future.v8_viteEnvironmentApi`, replacing `future.unstable_viteEnvironmentApi` ([#14595](https://github.com/remix-run/react-router/pull/14595))\n - โš ๏ธ This is a breaking change if you have begun using `future.unstable_viteEnvironmentApi` - please update your `react-router.config.ts`\n\n### Patch Changes\n\n- `react-router` - Fix a Framework Mode bug where the `defaultShouldRevalidate` parameter to `shouldRevalidate` would not be correct after `action` returned a 4xx/5xx response (`true` when it should have been `false`) ([#14592](https://github.com/remix-run/react-router/pull/14592))\n - If your `shouldRevalidate` function relied on that parameter, you may have seen unintended revalidations\n- `react-router` - Fix `fetcher.submit` failing with plain objects containing a `tagName` property ([#14534](https://github.com/remix-run/react-router/pull/14534))\n- `react-router` - Fix the promise returned from `useNavigate` in Framework/Data Mode so that it properly tracks the duration of `popstate` navigations (i.e., `navigate(-1)`) ([#14524](https://github.com/remix-run/react-router/pull/14524))\n- `react-router` - Preserve `statusText` on the `ErrorResponse` instance when throwing `data()` from a route handler ([#14555](https://github.com/remix-run/react-router/pull/14555))\n- `react-router` - Optimize `href()` to avoid backtracking regex on splat ([#14329](https://github.com/remix-run/react-router/pull/14329))\n- `@react-router/dev` - Fix internal type error in `useRoute` types that surfaces when `skipLibCheck` is disabled ([#14577](https://github.com/remix-run/react-router/pull/14577))\n- `@react-router/dev` - Load environment variables before evaluating `routes.ts` ([#14446](https://github.com/remix-run/react-router/pull/14446))\n - For example, you can now compute your routes based on [`VITE_`-prefixed environment variables](https://vite.dev/guide/env-and-mode#env-variables)\n\n ```ts\n // app/routes.ts\n import { type RouteConfig, route } from \"@react-router/dev/routes\";\n\n const routes: RouteConfig = [];\n\n // Only add the route when VITE_ENV_ROUTE is set\n if (import.meta.env.VITE_ENV_ROUTE === \"my-route\") {\n routes.push(route(\"my-route\", \"routes/my-route.tsx\"));\n }\n\n export default routes;\n ```\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `react-router` - Add `unstable_pattern` to the parameters for client side `unstable_onError` ([#14573](https://github.com/remix-run/react-router/pull/14573))\n- `react-router` - Refactor how `unstable_onError` is called internally by `RouterProvider` to avoid potential strict mode issues ([#14573](https://github.com/remix-run/react-router/pull/14573))\n- `react-router` - Add new `unstable_useTransitions` flag to routers to give users control over the usage of [`React.startTransition`](https://react.dev/reference/react/startTransition) and [`React.useOptimistic`](https://react.dev/reference/react/useOptimistic) ([#14524](https://github.com/remix-run/react-router/pull/14524))\n - Please see the [docs](https://reactrouter.com/7.10.0/explanation/react-transitions) for more information\n - Framework Mode + Data Mode:\n - ``/``\n - When left unset (current default behavior)\n - Router state updates are wrapped in `React.startTransition`\n - โš ๏ธ This can lead to buggy behaviors if you are wrapping your own navigations/fetchers in `React.startTransition`\n - You should set the flag to `true` if you run into this scenario to get the enhanced `useOptimistic` behavior (requires React 19)\n - When set to `true`\n - Router state updates remain wrapped in `React.startTransition` (as they are without the flag)\n - `Link`/`Form` navigations will be wrapped in `React.startTransition`\n - You can drop down to `useNavigate`/`useSubmit` if you wish to opt out of this outer `React.startTransition` call for the navigation\n - A subset of router state info will be surfaced to the UI _during_ navigations via `React.useOptimistic` (i.e., `useNavigation()`, `useFetchers()`, etc.)\n - โš ๏ธ This is a React 19 API so you must also be React 19 to opt into this flag for Framework/Data Mode\n - When set to `false`\n - The router will not leverage `React.startTransition` or `React.useOptimistic` on any navigations or state changes\n - Declarative Mode\n - ``\n - When left unset\n - Router state updates are wrapped in `React.startTransition`\n - When set to `true`\n - Router state updates remain wrapped in `React.startTransition` (as they are without the flag)\n - `Link`/`Form` navigations will be wrapped in `React.startTransition`\n - When set to `false`\n - The router will not leverage `React.startTransition` on any navigations or state changes\n\n**Full Changelog**: [`v7.9.6...v7.10.0`](https://github.com/remix-run/react-router/compare/react-router@7.9.6...react-router@7.10.0)\n\n## v7.9.6\n\nDate: 2025-11-13\n\n### Security Notice\n\nThis release addresses 1 security vulnerability:\n\n- [Unexpected external redirect via untrusted paths](https://github.com/remix-run/react-router/security/advisories/GHSA-9jcx-v3wj-wh4m)\n\n### Patch Changes\n\n- `react-router` - Properly handle ancestor thrown middleware errors before `next()` on fetcher submissions ([#14517](https://github.com/remix-run/react-router/pull/14517))\n- `react-router` - Fix issue with splat routes interfering with multiple calls to `patchRoutesOnNavigation` ([#14487](https://github.com/remix-run/react-router/pull/14487))\n- `react-router` - Normalize double-slashes in `resolvePath` ([#14529](https://github.com/remix-run/react-router/pull/14529))\n- `@react-router/dev` - Use a dynamic `import()` to load ESM-only `p-map` dependency to avoid issues on Node 20.18 and below ([#14492](https://github.com/remix-run/react-router/pull/14492))\n- `@react-router/dev` - Short circuit `HEAD` document requests before calling `renderToPipeableStream` in the default `entry.server.tsx` to more closely align with the [spec](https://httpwg.org/specs/rfc9110.html#HEAD) ([#14488](https://github.com/remix-run/react-router/pull/14488))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `react-router` - Add `location`/`params` as arguments to client-side `unstable_onError` to permit enhanced error reporting ([#14509](https://github.com/remix-run/react-router/pull/14509))\n - โš ๏ธ This is a breaking change if you've already adopted `unstable_onError`\n - The second parameter has changed to an object including `errorInfo`, `location`, and `params`:\n\n ```tsx\n // \n // \n\n // Before\n function errorHandler(error: unknown, errorInfo?: React.errorInfo) {\n /*...*/\n }\n\n // After\n function errorHandler(\n error: unknown,\n info: {\n location: Location;\n params: Params;\n errorInfo?: React.ErrorInfo;\n },\n ) {\n /*...*/\n }\n ```\n\n**Full Changelog**: [`v7.9.5...v7.9.6`](https://github.com/remix-run/react-router/compare/react-router@7.9.5...react-router@7.9.6)\n\n## v7.9.5\n\nDate: 2025-10-29\n\n### What's Changed\n\n#### Instrumentation (unstable)\n\nThis release adds new `unstable_instrumentation` APIs that will allow you to add runtime instrumentation logic to various aspects of your application (server handler, client navigations/fetches, loaders, actions, middleware, `route.lazy`). For more information, please see the [docs](https://reactrouter.com/7.9.5/how-to/instrumentation).\n\n### Patch Changes\n\n- `react-router` - Ensure action handlers run for routes with middleware even if no loader is present ([#14443](https://github.com/remix-run/react-router/pull/14443))\n- `@react-router/dev` - Ensure route navigation doesn't remove CSS `link` elements used by dynamic imports ([#14463](https://github.com/remix-run/react-router/pull/14463))\n- `@react-router/dev` - Typegen: only register route module types for routes within the app directory ([#14439](https://github.com/remix-run/react-router/pull/14439))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `react-router` - Move `unstable_RSCHydratedRouter` and utils to `react-router/dom` export ([#14457](https://github.com/remix-run/react-router/pull/14457))\n- `react-router` - Add a type-safe `handle` field to `unstable_useRoute()` ([#14462](https://github.com/remix-run/react-router/pull/14462))\n\n For example:\n\n ```ts\n // app/routes/admin.tsx\n const handle = { hello: \"world\" };\n ```\n\n ```ts\n // app/routes/some-other-route.tsx\n export default function Component() {\n const admin = useRoute(\"routes/admin\");\n if (!admin) throw new Error(\"Not nested within 'routes/admin'\");\n console.log(admin.handle);\n // ^? { hello: string }\n }\n ```\n\n- `react-router` - Add `unstable_instrumentations` API to allow users to add observability to their apps by instrumenting route loaders, actions, middlewares, lazy, as well as server-side request handlers and client side navigations/fetches ([#14412](https://github.com/remix-run/react-router/pull/14412))\n - Framework Mode:\n - `entry.server.tsx`: `export const unstable_instrumentations = [...]`\n - `entry.client.tsx`: ``\n - Data Mode\n - `createBrowserRouter(routes, { unstable_instrumentations: [...] })`\n- `react-router` - Add a new `unstable_pattern` parameter to loaders/actions/middleware which contains the un-interpolated route pattern (i.e., `/blog/:slug`) which is useful for aggregating logs/metrics by route in instrumentation code ([#14412](https://github.com/remix-run/react-router/pull/14412))\n- `@react-router/dev` - Introduce a `prerender.unstable_concurrency` option, to support running the pre-rendering concurrently, potentially speeding up the build ([#14380](https://github.com/remix-run/react-router/pull/14380))\n\n**Full Changelog**: [`v7.9.4...v7.9.5`](https://github.com/remix-run/react-router/compare/react-router@7.9.4...react-router@7.9.5)\n\n## v7.9.4\n\nDate: 2025-10-08\n\n### Security Notice\n\nThis release addresses 1 security vulnerability:\n\n- [Unauthorized file access when using `createFileSessionStorage()` with unsigned cookies](https://github.com/remix-run/react-router/security/advisories/GHSA-9583-h5hc-x8cw)\n\n### What's Changed\n\n#### `useRoute()` (unstable)\n\nThis release includes a new `unstable_useRoute()` hook that provides a type-safe way to access route `loaderData`/`actionData` from a specific route in Framework Mode. Think if it like a better version of `useRouteLoaderData` that works with the typegen system and also supports `actionData`. Check out the changelog entry below for more information.\n\n### Patch Changes\n\n- `@react-router/dev` - Update `valibot` dependency to `^1.1.0` ([#14379](https://github.com/remix-run/react-router/pull/14379))\n- `@react-router/node` - Validate format of incoming session ids in `createFileSessionStorage` ([#14426](https://github.com/remix-run/react-router/pull/14426))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `react-router` - handle external redirects in from server actions ([#14400](https://github.com/remix-run/react-router/pull/14400))\n- `react-router` - New (unstable) `useRoute` hook for accessing data from specific routes ([#14407](https://github.com/remix-run/react-router/pull/14407))\n\n For example, let's say you have an `admin` route somewhere in your app and you want any child routes of `admin` to all have access to the `loaderData` and `actionData` from `admin.`\n\n ```tsx\n // app/routes/admin.tsx\n import { Outlet } from \"react-router\";\n\n export const loader = () => ({ message: \"Hello, loader!\" });\n\n export const action = () => ({ count: 1 });\n\n export default function Component() {\n return (\n
\n {/* ... */}\n \n {/* ... */}\n
\n );\n }\n ```\n\n You might even want to create a reusable widget that all of the routes nested under `admin` could use:\n\n ```tsx\n import { unstable_useRoute as useRoute } from \"react-router\";\n\n export function AdminWidget() {\n // How to get `message` and `count` from `admin` route?\n }\n ```\n\n In framework mode, `useRoute` knows all your app's routes and gives you TS errors when invalid route IDs are passed in:\n\n ```tsx\n export function AdminWidget() {\n const admin = useRoute(\"routes/dmin\");\n // ^^^^^^^^^^^\n }\n ```\n\n `useRoute` returns `undefined` if the route is not part of the current page:\n\n ```tsx\n export function AdminWidget() {\n const admin = useRoute(\"routes/admin\");\n if (!admin) {\n throw new Error(`AdminWidget used outside of \"routes/admin\"`);\n }\n }\n ```\n\n Note: the `root` route is the exception since it is guaranteed to be part of the current page.\n As a result, `useRoute` never returns `undefined` for `root`.\n\n `loaderData` and `actionData` are marked as optional since they could be accessed before the `action` is triggered or after the `loader` threw an error:\n\n ```tsx\n export function AdminWidget() {\n const admin = useRoute(\"routes/admin\");\n if (!admin) {\n throw new Error(`AdminWidget used outside of \"routes/admin\"`);\n }\n const { loaderData, actionData } = admin;\n console.log(loaderData);\n // ^? { message: string } | undefined\n console.log(actionData);\n // ^? { count: number } | undefined\n }\n ```\n\n If instead of a specific route, you wanted access to the _current_ route's `loaderData` and `actionData`, you can call `useRoute` without arguments:\n\n ```tsx\n export function AdminWidget() {\n const currentRoute = useRoute();\n currentRoute.loaderData;\n currentRoute.actionData;\n }\n ```\n\n This usage is equivalent to calling `useLoaderData` and `useActionData`, but consolidates all route data access into one hook: `useRoute`.\n\n Note: when calling `useRoute()` (without a route ID), TS has no way to know which route is the current route.\n As a result, `loaderData` and `actionData` are typed as `unknown`.\n If you want more type-safety, you can either narrow the type yourself with something like `zod` or you can refactor your app to pass down typed props to your `AdminWidget`:\n\n ```tsx\n export function AdminWidget({\n message,\n count,\n }: {\n message: string;\n count: number;\n }) {\n /* ... */\n }\n ```\n\n**Full Changelog**: [`v7.9.3...v7.9.4`](https://github.com/remix-run/react-router/compare/react-router@7.9.3...react-router@7.9.4)\n\n## v7.9.3\n\nDate: 2025-09-26\n\n### Patch Changes\n\n- `react-router` - Fix Data Mode regression causing a 404 during initial load in when `middleware` exists without any `loader` functions ([#14393](https://github.com/remix-run/react-router/pull/14393))\n- `react-router` - Do not try to use `turbo-stream` to decode CDN errors that never reached the server ([#14385](https://github.com/remix-run/react-router/pull/14385))\n - This was logic we used to have in Remix v2 that got lost in the adoption of Single Fetch\n - This permits the actual CDN error to bubble to the `ErrorBoundary` instead of a generic _\"Unable to decode turbo-stream response\"_ error\n\n**Full Changelog**: [`v7.9.2...v7.9.3`](https://github.com/remix-run/react-router/compare/react-router@7.9.2...react-router@7.9.3)\n\n## v7.9.2\n\nDate: 2025-09-24\n\n### What's Changed\n\nThis release contains a handful of bug fixes, but we think you'll be most excited about the new unstable stuff ๐Ÿ˜‰.\n\n#### RSC Framework Mode (unstable)\n\nThis release includes our first release of unstable support for RSC in Framework Mode! You can read more about it in our [blog post](https://remix.run/blog/rsc-framework-mode-preview) and the [docs](https://reactrouter.com/how-to/react-server-components#rsc-framework-mode).\n\n#### Fetcher Reset (unstable)\n\nThis release also includes a new (long-requested) `fetcher.unstable_reset()` API to reset fetchers back to their initial `idle` state.\n\n### Patch Changes\n\n- `react-router` - Ensure client-side router runs client `middleware` during initialization data load (if required) even if no loaders exist ([#14348](https://github.com/remix-run/react-router/pull/14348))\n- `react-router` - Fix `middleware` prop not being supported on `` when used with a data router via `createRoutesFromElements` ([#14357](https://github.com/remix-run/react-router/pull/14357))\n- `react-router` - Update `createRoutesStub` to work with `middleware` ([#14348](https://github.com/remix-run/react-router/pull/14348))\n - You will need to set the `` flag to enable the proper `context` type\n- `react-router` - Update Lazy Route Discovery manifest requests to use a singular comma-separated `paths` query param instead of repeated `p` query params ([#14321](https://github.com/remix-run/react-router/pull/14321))\n - This is because Cloudflare has a hard limit of 100 URL search param key/value pairs when used as a key for caching purposes\n - If more that 100 paths were included, the cache key would be incomplete and could produce false-positive cache hits\n- `react-router` - Fail gracefully on manifest version mismatch logic if `sessionStorage` access is blocked ([#14335](https://github.com/remix-run/react-router/pull/14335))\n- `react-router` - Update `useOutlet` returned element to have a stable identity in-between route changes ([#13382](https://github.com/remix-run/react-router/pull/13382))\n- `react-router` - Handle encoded question mark and hash characters in ancestor splat routes ([#14249](https://github.com/remix-run/react-router/pull/14249))\n- `@react-router/dev` - Switch internal vite plugin Response logic to use `@remix-run/node-fetch-server` ([#13927](https://github.com/remix-run/react-router/pull/13927))\n- `@react-router/dev` - Fix `presets` `future` flags being ignored during config resolution ([#14369](https://github.com/remix-run/react-router/pull/14369))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `react-router` - Add `fetcher.unstable_reset()` API ([#14206](https://github.com/remix-run/react-router/pull/14206))\n- `react-router` - In RSC Data Mode, handle SSR'd client errors and re-try in the browser ([#14342](https://github.com/remix-run/react-router/pull/14342))\n- `react-router` - Enable full transition support for the RSC router ([#14362](https://github.com/remix-run/react-router/pull/14362))\n- `@react-router/dev` - Add unstable support for RSC Framework Mode ([#14336](https://github.com/remix-run/react-router/pull/14336))\n- `@react-router/serve` - Disable `compression()` middleware in RSC framework mode ([#14381](https://github.com/remix-run/react-router/pull/14381))\n\n**Full Changelog**: [`v7.9.1...v7.9.2`](https://github.com/remix-run/react-router/compare/react-router@7.9.1...react-router@7.9.2)\n\n## v7.9.1\n\nDate: 2025-09-12\n\n### Patch Changes\n\n- Fix internal `Future` interface naming from `middleware` -> `v8_middleware` ([#14327](https://github.com/remix-run/react-router/pull/14327))\n\n**Full Changelog**: [`v7.9.0...v7.9.1`](https://github.com/remix-run/react-router/compare/react-router@7.9.0...react-router@7.9.1)\n\n## v7.9.0\n\nDate: 2025-09-12\n\n### Security Notice\n\nThis release addresses 1 security vulnerability:\n\n- [XSS via Meta component when generating script:ld+json tags](https://github.com/remix-run/react-router/security/advisories/GHSA-3cgp-3xvw-98x8)\n\n### What's Changed\n\n#### Stable Middleware and Context APIs\n\nWe have removed the `unstable_` prefix from the following APIs and they are now considered stable and ready for production use:\n\n- [`RouterContextProvider`](https://reactrouter.com/api/utils/RouterContextProvider)\n- [`createContext`](https://reactrouter.com/api/utils/createContext)\n- `createBrowserRouter` [`getContext`](https://reactrouter.com/api/data-routers/createBrowserRouter#optsgetcontext) option\n- `` [`getContext`](https://reactrouter.com/api/framework-routers/HydratedRouter#getcontext) prop\n\nPlease see the [Middleware Docs](https://reactrouter.com/how-to/middleware), the [Middleware RFC](https://github.com/remix-run/remix/discussions/7642), and the [Client-side Context RFC](https://github.com/remix-run/react-router/discussions/9856) for more information.\n\n### Minor Changes\n\n- Stabilize middleware and context APIs ([#14215](https://github.com/remix-run/react-router/pull/14215))\n\n### Patch Changes\n\n- `react-router` - Update `href()` to correctly process routes that have an extension after the parameter or are a single optional parameter ([#13797](https://github.com/remix-run/react-router/pull/13797))\n- `react-router` - Escape HTML in `meta()` JSON-LD content ([#14316](https://github.com/remix-run/react-router/pull/14316))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `react-router` - RSC: Add react-server `Await` component implementation ([#14261](https://github.com/remix-run/react-router/pull/14261))\n- `react-router` - RSC: Fix hydration errors for routes that only have client loaders when using RSC in Data Mode along with a custom basename ([#14264](https://github.com/remix-run/react-router/pull/14264))\n- `react-router` - RSC: Make `href` function available in a `react-server` context ([#14262](https://github.com/remix-run/react-router/pull/14262))\n- `react-router` - RSC: Decode each time `getPayload()` is called to allow for \"in-context\" decoding and hoisting of contextual assets ([#14248](https://github.com/remix-run/react-router/pull/14248))\n\n**Full Changelog**: [`v7.8.2...v7.9.0`](https://github.com/remix-run/react-router/compare/react-router@7.8.2...react-router@7.9.0)\n\n## v7.8.2\n\nDate: 2025-08-22\n\n### Patch Changes\n\n- `react-router` - Maintain `ReadonlyMap` and `ReadonlySet` types in server response data. ([#13092](https://github.com/remix-run/react-router/pull/13092))\n- `react-router` - Fix `basename` usage without a leading slash in data routers ([#11671](https://github.com/remix-run/react-router/pull/11671))\n- `react-router` - Fix `TypeError` if you throw from `patchRoutesOnNavigation` when no partial matches exist ([#14198](https://github.com/remix-run/react-router/pull/14198))\n- `react-router` - Properly escape interpolated param values in `generatePath()` ([#13530](https://github.com/remix-run/react-router/pull/13530))\n- `@react-router/dev` - Fix potential memory leak in default `entry.server` ([#14200](https://github.com/remix-run/react-router/pull/14200))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n**Client-side `onError`**\n\n- `react-router` - Add ``/`` prop for client side error reporting ([#14162](https://github.com/remix-run/react-router/pull/14162))\n\n**Middleware**\n\n- `react-router` - Delay serialization of `.data` redirects to 202 responses until after middleware chain ([#14205](https://github.com/remix-run/react-router/pull/14205))\n- `react-router` - Update client middleware so it returns the `dataStrategy` results up the chain allowing for more advanced post-processing middleware ([#14151](https://github.com/remix-run/react-router/pull/14151), [#14212](https://github.com/remix-run/react-router/pull/14212))\n- `react-router` - Remove Data Mode `future.unstable_middleware` flag from `createBrowserRouter` ([#14213](https://github.com/remix-run/react-router/pull/14213))\n - This is only needed as a Framework Mode flag because of the route modules and the `getLoadContext` type behavior change\n - In Data Mode, it's an opt-in feature because it's just a new property on a route object, so there's no behavior changes that necessitate a flag\n\n**RSC**\n\n- `react-router` - Allow opting out of revalidation on server actions with hidden `$SKIP_REVALIDATION` input ([#14154](https://github.com/remix-run/react-router/pull/14154))\n\n**Full Changelog**: [`v7.8.1...v7.8.2`](https://github.com/remix-run/react-router/compare/react-router@7.8.1...react-router@7.8.2)\n\n## v7.8.1\n\nDate: 2025-08-15\n\n### Patch Changes\n\n- `react-router` - Fix usage of optional path segments in nested routes defined using absolute paths ([#14135](https://github.com/remix-run/react-router/pull/14135))\n- `react-router` - Fix optional static segment matching in `matchPath` ([#11813](https://github.com/remix-run/react-router/pull/11813))\n- `react-router` - Fix pre-rendering when a `basename` is set with `ssr:false` ([#13791](https://github.com/remix-run/react-router/pull/13791))\n- `react-router` - Properly convert returned/thrown `data()` values to `Response` instances via `Response.json()` in resource routes and middleware ([#14159](https://github.com/remix-run/react-router/pull/14159), [#14181](https://github.com/remix-run/react-router/pull/14181))\n- `@react-router/dev` - Update generated `Route.MetaArgs` type so `loaderData` is only potentially undefined when an `ErrorBoundary` export is present ([#14173](https://github.com/remix-run/react-router/pull/14173))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n**Middleware**\n\n- `react-router` - Bubble client pre-`next` middleware errors to the shallowest ancestor that needs to load, not strictly the shallowest ancestor with a loader ([#14150](https://github.com/remix-run/react-router/pull/14150))\n- `react-router` - Propagate non-redirect `Response` values thrown from middleware to the error boundary on document/data requests ([#14182](https://github.com/remix-run/react-router/pull/14182))\n\n**RSC**\n\n- `react-router` - Provide `isRouteErrorResponse` utility in `react-server` environments ([#14166](https://github.com/remix-run/react-router/pull/14166))\n- `react-router` - Handle `meta` and `links` Route Exports in RSC Data Mode ([#14136](https://github.com/remix-run/react-router/pull/14136))\n\n**Full Changelog**: [`v7.8.0...v7.8.1`](https://github.com/remix-run/react-router/compare/react-router@7.8.0...react-router@7.8.1)\n\n## v7.8.0\n\nDate: 2025-08-07\n\n### What's Changed\n\n#### Consistently named `loaderData` values\n\nEver noticed the discrepancies in loader data values handed to you by the framework? Like, we call it `loaderData` in your component props, but then `match.data` in your matches? Yeah, us too - as well as some keen-eyed React Router users who raised this in a proposal. We've added new `loaderData` fields alongside existing `data` fields in a few lingering spots to align with the `loaderData` naming used in the new `Route.*` APIs.\n\n#### Improvements/fixes to the middleware APIs (unstable)\n\nThe biggest set of changes in `7.8.0` are to the `unstable_middleware` API's as we move closer to stabilizing them. If you've adopted the middleware APIs for early testing, please read the middleware changes below carefully. We hope to stabilize these soon so please let us know of any feedback you have on the API's in their current state!\n\n### Minor Changes\n\n- `react-router` - Add `nonce` prop to `Links` & `PrefetchPageLinks` ([#14048](https://github.com/remix-run/react-router/pull/14048))\n- `react-router` - Add `loaderData` arguments/properties alongside existing `data` arguments/properties to provide consistency and clarity between `loaderData` and `actionData` across the board ([#14047](https://github.com/remix-run/react-router/pull/14047))\n - Updated types: `Route.MetaArgs`, `Route.MetaMatch`, `MetaArgs`, `MetaMatch`, `Route.ComponentProps.matches`, `UIMatch`\n - `@deprecated` warnings have been added to the existing `data` properties to point users to new `loaderData` properties, in preparation for removing the `data` properties in a future major release\n\n### Patch Changes\n\n- `react-router` - Prevent _\"Did not find corresponding fetcher result\"_ console error when navigating during a `fetcher.submit` revalidation ([#14114](https://github.com/remix-run/react-router/pull/14114))\n- `react-router` - Switch Lazy Route Discovery manifest URL generation to use a standalone `URLSearchParams` instance instead of `URL.searchParams` to avoid a major performance bottleneck in Chrome ([#14084](https://github.com/remix-run/react-router/pull/14084))\n- `react-router` - Adjust internal RSC usage of `React.use` to avoid Webpack compilation errors when using React 18 ([#14113](https://github.com/remix-run/react-router/pull/14113))\n- `react-router` - Remove dependency on `@types/node` in TypeScript declaration files ([#14059](https://github.com/remix-run/react-router/pull/14059))\n- `react-router` - Fix types for `UIMatch` to reflect that the `loaderData`/`data` properties may be `undefined` ([#12206](https://github.com/remix-run/react-router/pull/12206))\n - When an `ErrorBoundary` is being rendered, not all active matches will have loader data available, since it may have been their `loader` that threw to trigger the boundary\n - The `UIMatch.data` type was not correctly handing this and would always reflect the presence of data, leading to the unexpected runtime errors when an `ErrorBoundary` was rendered\n - โš ๏ธ This may cause some type errors to show up in your code for unguarded `match.data` accesses - you should properly guard for `undefined` values in those scenarios.\n\n ```tsx\n // app/root.tsx\n export function loader() {\n someFunctionThatThrows(); // โŒ Throws an Error\n return { title: \"My Title\" };\n }\n\n export function Layout({ children }: { children: React.ReactNode }) {\n let matches = useMatches();\n let rootMatch = matches[0] as UIMatch>>;\n // ^ rootMatch.data is currently incorrectly typed here, so TypeScript does\n // not complain if you do the following which throws an error at runtime:\n let { title } = rootMatch.data; // ๐Ÿ’ฅ\n\n return ...;\n }\n ```\n\n- `@react-router/dev` - Fix rename without mkdir in Vite plugin ([#14105](https://github.com/remix-run/react-router/pull/14105))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n**RSC**\n\n- `react-router` - Fix Data Mode issue where routes that return `false` from `shouldRevalidate` would be replaced by an `` ([#14071](https://github.com/remix-run/react-router/pull/14071))\n- `react-router` - Proxy server action side-effect redirects from actions for document and `callServer` requests ([#14131](https://github.com/remix-run/react-router/pull/14131))\n\n**Middleware**\n\n- `react-router` - Change the `unstable_getContext` signature on `RouterProvider`, `HydratedRouter`, and `unstable_RSCHydratedRouter` so that it returns an `unstable_RouterContextProvider` instance instead of a `Map` used to construct the instance internally ([#14097](https://github.com/remix-run/react-router/pull/14097))\n - See the [docs](https://reactrouter.com/api/data-routers/createBrowserRouter#optsunstable_getcontext) for more information\n - โš ๏ธ This is a breaking change if you have adopted the `unstable_getContext` prop\n- `react-router` - Run client middleware on client navigations even if no loaders exist ([#14106](https://github.com/remix-run/react-router/pull/14106))\n- `react-router` - Convert internal middleware implementations to use the new `unstable_generateMiddlewareResponse` API ([#14103](https://github.com/remix-run/react-router/pull/14103))\n- `react-router` - Ensure resource route errors go through `handleError` w/middleware enabled ([#14078](https://github.com/remix-run/react-router/pull/14078))\n- `react-router` - Propagate returned `Response` from server middleware if `next` wasn't called ([#14093](https://github.com/remix-run/react-router/pull/14093))\n- `react-router` - Allow server middlewares to return `data()` values which will be converted into a `Response` ([#14093](https://github.com/remix-run/react-router/pull/14093), [#14128](https://github.com/remix-run/react-router/pull/14128))\n- `react-router` - Update middleware error handling so that the `next` function never throws and instead handles any middleware errors at the proper `ErrorBoundary` and returns the `Response` up through the ancestor `next` function ([#14118](https://github.com/remix-run/react-router/pull/14118))\n - See the [error handling docs](https://reactrouter.com/how-to/middleware#next-and-error-handling) for more information\n - โš ๏ธ This changes existing functionality so if you are currently wrapping `next` calls in `try`/`catch` you should be able to remove those\n- `react-router` - Bubble client-side middleware errors prior to `next` to the appropriate ancestor error boundary ([#14138](https://github.com/remix-run/react-router/pull/14138))\n- `react-router` - When middleware is enabled, make the `context` parameter read-only (`Readonly`) so that TypeScript will not allow you to write arbitrary fields to it in loaders, actions, or middleware. ([#14097](https://github.com/remix-run/react-router/pull/14097))\n- `react-router` - Rename and alter the signature/functionality of the `unstable_respond` API in `staticHandler.query`/`staticHandler.queryRoute` ([#14103](https://github.com/remix-run/react-router/pull/14103))\n - This only impacts users using `createStaticHandler()` for manual data loading during non-Framework Mode SSR\n - The API has been renamed to `unstable_generateMiddlewareResponse` for clarity\n - The main functional change is that instead of running the loaders/actions before calling `unstable_respond` and handing you the result, we now pass a `query`/`queryRoute` function as a parameter and you execute the loaders/actions inside your callback, giving you full access to pre-processing and error handling\n - The `query` version of the API now has a signature of `(query: (r: Request) => Promise) => Promise`\n - The `queryRoute` version of the API now has a signature of `(queryRoute: (r: Request) => Promise) => Promise`\n - This allows for more advanced usages such as running logic before/after calling `query` and direct error handling of errors thrown from query\n - โš ๏ธ This is a breaking change if you've adopted the `staticHandler` `unstable_respond` API\n\n ```tsx\n let response = await staticHandler.query(request, {\n requestContext: new unstable_RouterContextProvider(),\n async unstable_generateMiddlewareResponse(query) {\n try {\n // At this point we've run middleware top-down so we need to call the\n // handlers and generate the Response to bubble back up the middleware\n let result = await query(request);\n if (isResponse(result)) {\n return result; // Redirects, etc.\n }\n return await generateHtmlResponse(result);\n } catch (error: unknown) {\n return generateErrorResponse(error);\n }\n },\n });\n ```\n\n- `@react-router/{architect,cloudflare,express,node}` - Change the `getLoadContext` signature (`type GetLoadContextFunction`) when `future.unstable_middleware` is enabled so that it returns an `unstable_RouterContextProvider` instance instead of a `Map` used to construct the instance internally ([#14097](https://github.com/remix-run/react-router/pull/14097))\n - This also removes the `type unstable_InitialContext` export\n - See the [middleware `getLoadContext` docs](https://reactrouter.com/how-to/middleware#changes-to-getloadcontextapploadcontext) for more information\n - โš ๏ธ This is a breaking change if you have adopted middleware and are using a custom server with a `getLoadContext` function\n\n### Changes by Package\n\n- [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.8.0/packages/create-react-router/CHANGELOG.md#780)\n- [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.8.0/packages/react-router/CHANGELOG.md#780)\n- [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.8.0/packages/react-router-architect/CHANGELOG.md#780)\n- [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.8.0/packages/react-router-cloudflare/CHANGELOG.md#780)\n- [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.8.0/packages/react-router-dev/CHANGELOG.md#780)\n- [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.8.0/packages/react-router-express/CHANGELOG.md#780)\n- [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.8.0/packages/react-router-fs-routes/CHANGELOG.md#780)\n- [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.8.0/packages/react-router-node/CHANGELOG.md#780)\n- [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.8.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#780)\n- [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.8.0/packages/react-router-serve/CHANGELOG.md#780)\n\n**Full Changelog**: [`v7.7.1...v7.8.0`](https://github.com/remix-run/react-router/compare/react-router@7.7.1...react-router@7.8.0)\n\n## v7.7.1\n\nDate: 2025-07-24\n\n### Patch Changes\n\n- `@react-router/dev` - Update to Prettier v3 for formatting when running `react-router reveal --no-typescript` ([#14049](https://github.com/remix-run/react-router/pull/14049))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `react-router` - RSC Data Mode: fix bug where routes with errors weren't forced to revalidate when `shouldRevalidate` returned `false` ([#14026](https://github.com/remix-run/react-router/pull/14026))\n- `react-router` - RSC Data Mode: fix `Matched leaf route at location \"/...\" does not have an element or Component` warnings when error boundaries are rendered ([#14021](https://github.com/remix-run/react-router/pull/14021))\n\n**Full Changelog**: [`v7.7.0...v7.7.1`](https://github.com/remix-run/react-router/compare/react-router@7.7.0...react-router@7.7.1)\n\n## v7.7.0\n\nDate: 2025-07-16\n\n### What's Changed\n\n#### Unstable RSC APIs\n\nWe're excited to introduce experimental support for RSC in Data Mode via the following new APIs:\n\n- [`unstable_RSCHydratedRouter`](https://reactrouter.com/api/rsc/RSCHydratedRouter)\n- [`unstable_RSCStaticRouter`](https://reactrouter.com/api/rsc/RSCStaticRouter)\n- [`unstable_createCallServer`](https://reactrouter.com/api/rsc/createCallServer)\n- [`unstable_getRSCStream`](https://reactrouter.com/api/rsc/getRSCStream)\n- [`unstable_matchRSCServerRequest`](https://reactrouter.com/api/rsc/matchRSCServerRequest)\n- [`unstable_routeRSCServerRequest`](https://reactrouter.com/api/rsc/routeRSCServerRequest)\n\nFor more information, check out the [blog post](https://remix.run/blog/react-router-and-react-server-components) and the [RSC Docs](https://reactrouter.com/how-to/react-server-components).\n\n### Minor Changes\n\n- `create-react-router` - Add Deno as a supported and detectable package manager. Note that this detection will only work with Deno versions 2.0.5 and above. If you are using an older version version of Deno then you must specify the --package-manager CLI flag set to `deno`. ([#12327](https://github.com/remix-run/react-router/pull/12327))\n- `@react-router/remix-config-routes-adapter` - Export `DefineRouteFunction` type alongside `DefineRoutesFunction` ([#13945](https://github.com/remix-run/react-router/pull/13945))\n\n### Patch Changes\n\n- `react-router` - Handle `InvalidCharacterError` when validating cookie signature ([#13847](https://github.com/remix-run/react-router/pull/13847))\n- `react-router` - Pass a copy of `searchParams` to the `setSearchParams` callback function to avoid mutations of the internal `searchParams` instance ([#12784](https://github.com/remix-run/react-router/pull/12784))\n - This causes bugs if you mutate the current stateful `searchParams` when a navigation is blocked because the internal instance gets out of sync with `useLocation().search`\n- `react-router` - Support invalid `Date` in `turbo-stream` v2 fork ([#13684](https://github.com/remix-run/react-router/pull/13684))\n- `react-router` - In Framework Mode, clear critical CSS in development after initial render ([#13872](https://github.com/remix-run/react-router/pull/13872), [#13995](https://github.com/remix-run/react-router/pull/13995))\n- `react-router` - Strip search parameters from `patchRoutesOnNavigation` `path` param for fetcher calls ([#13911](https://github.com/remix-run/react-router/pull/13911))\n- `react-router` - Skip scroll restoration on `useRevalidator()` calls because they're not new locations ([#13671](https://github.com/remix-run/react-router/pull/13671))\n- `react-router` - Support unencoded UTF-8 routes in prerender config with `ssr` set to `false` ([#13699](https://github.com/remix-run/react-router/pull/13699))\n- `react-router` - Do not throw if the url hash is not a valid URI component ([#13247](https://github.com/remix-run/react-router/pull/13247))\n- `react-router` - Remove `Content-Length` header from Single Fetch responses ([#13902](https://github.com/remix-run/react-router/pull/13902))\n- `react-router` - Fix a regression in `createRoutesStub` introduced with the middleware feature ([#13946](https://github.com/remix-run/react-router/pull/13946))\n - As part of that work we altered the signature to align with the new middleware APIs without making it backwards compatible with the prior `AppLoadContext` API\n - This permitted `createRoutesStub` to work if you were opting into middleware and the updated `context` typings, but broke `createRoutesStub` for users not yet opting into middleware\n - We've reverted this change and re-implemented it in such a way that both sets of users can leverage it\n - โš ๏ธ This may be a breaking bug for if you have adopted the unstable Middleware feature and are using `createRoutesStub` with the updated API.\n\n ```tsx\n // If you have not opted into middleware, the old API should work again\n let context: AppLoadContext = {\n /*...*/\n };\n let Stub = createRoutesStub(routes, context);\n\n // If you have opted into middleware, you should now pass an instantiated\n // `unstable_routerContextProvider` instead of a `getContext` factory function.\n let context = new unstable_RouterContextProvider();\n context.set(SomeContext, someValue);\n let Stub = createRoutesStub(routes, context);\n ```\n\n- `@react-router/dev` - Update `vite-node` to `^3.2.2` to support Vite 7 ([#13781](https://github.com/remix-run/react-router/pull/13781))\n- `@react-router/dev` - Properly handle `https` protocol in dev mode ([#13746](https://github.com/remix-run/react-router/pull/13746))\n- `@react-router/dev` - Fix missing styles when Vite's `build.cssCodeSplit` option is disabled ([#13943](https://github.com/remix-run/react-router/pull/13943))\n- `@react-router/dev` - Allow `.mts` and `.mjs` extensions for route config file ([#13931](https://github.com/remix-run/react-router/pull/13931))\n- `@react-router/dev` - Fix prerender file locations when `cwd` differs from project root ([#13824](https://github.com/remix-run/react-router/pull/13824))\n- `@react-router/dev` - Improve chunk error logging when a chunk cannot be found during the build ([#13799](https://github.com/remix-run/react-router/pull/13799))\n- `@react-router/dev` - Fix incorrectly configured `externalConditions` which had enabled `module` condition for externals and broke builds with certain packages (like Emotion) ([#13871](https://github.com/remix-run/react-router/pull/13871))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- Add unstable RSC support for Data Mode ([#13700](https://github.com/remix-run/react-router/pull/13700))\n - For more information, see the [RSC documentation](https://reactrouter.com/how-to/react-server-components)\n\n### Changes by Package\n\n- [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.7.0/packages/create-react-router/CHANGELOG.md#770)\n- [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.7.0/packages/react-router/CHANGELOG.md#770)\n- [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.7.0/packages/react-router-architect/CHANGELOG.md#770)\n- [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.7.0/packages/react-router-cloudflare/CHANGELOG.md#770)\n- [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.7.0/packages/react-router-dev/CHANGELOG.md#770)\n- [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.7.0/packages/react-router-express/CHANGELOG.md#770)\n- [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.7.0/packages/react-router-fs-routes/CHANGELOG.md#770)\n- [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.7.0/packages/react-router-node/CHANGELOG.md#770)\n- [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.7.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#770)\n- [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.7.0/packages/react-router-serve/CHANGELOG.md#770)\n\n**Full Changelog**: [`v7.6.3...v7.7.0`](https://github.com/remix-run/react-router/compare/react-router@7.6.3...react-router@7.7.0)\n\n## v7.6.3\n\nDate: 2025-06-27\n\n### Patch Changes\n\n- `react-router` - Do not serialize types for `useRouteLoaderData` ([#13752](https://github.com/remix-run/react-router/pull/13752))\n - For types to distinguish a `clientLoader` from a `serverLoader`, you MUST annotate `clientLoader` args:\n\n ```ts\n // ๐Ÿ‘‡ annotation required to skip serializing types\n export function clientLoader({}: Route.ClientLoaderArgs) {\n return { fn: () => \"earth\" };\n }\n\n function SomeComponent() {\n const data = useRouteLoaderData(\"routes/this-route\");\n const planet = data?.fn() ?? \"world\";\n return

Hello, {planet}!

;\n }\n ```\n\n- `@react-router/cloudflare` - Remove `tsup` from `peerDependencies` ([#13757](https://github.com/remix-run/react-router/pull/13757))\n- `@react-router/dev` - Add Vite 7 support ([#13748](https://github.com/remix-run/react-router/pull/13748))\n- `@react-router/dev` - Skip `package.json` resolution checks when a custom `entry.server.(j|t)sx` file is provided ([#13744](https://github.com/remix-run/react-router/pull/13744))\n- `@react-router/dev` - Add validation for a route's id not being 'root' ([#13792](https://github.com/remix-run/react-router/pull/13792))\n- `@react-router/fs-routes` `@react-router/remix-config-routes-adapter` - Use `replaceAll` for normalizing windows file system slashes ([#13738](https://github.com/remix-run/react-router/pull/13738))\n- `@react-router/node` - Remove old \"install\" package exports ([#13762](https://github.com/remix-run/react-router/pull/13762))\n\n**Full Changelog**: [`v7.6.2...v7.6.3`](https://github.com/remix-run/react-router/compare/react-router@7.6.2...react-router@7.6.3)\n\n## v7.6.2\n\nDate: 2025-06-03\n\n### Patch Changes\n\n- `create-react-router` - Update `tar-fs` ([#13675](https://github.com/remix-run/react-router/pull/13675))\n- `react-router` - (INTERNAL) Slight refactor of internal `headers()` function processing for use with RSC ([#13639](https://github.com/remix-run/react-router/pull/13639))\n- `react-router` `@react-router/dev` - Avoid additional `with-props` chunk in Framework Mode by moving route module component prop logic from the Vite plugin to `react-router` ([#13650](https://github.com/remix-run/react-router/pull/13650))\n- `@react-router/dev` - When `future.unstable_viteEnvironmentApi` is enabled and an absolute Vite `base` has been configured, ensure critical CSS is handled correctly during development ([#13598](https://github.com/remix-run/react-router/pull/13598))\n- `@react-router/dev` - Update `vite-node` ([#13673](https://github.com/remix-run/react-router/pull/13673))\n- `@react-router/dev` - Fix typegen for non-{.js,.jsx,.ts,.tsx} routes like .mdx ([#12453](https://github.com/remix-run/react-router/pull/12453))\n- `@react-router/dev` - Fix href types for optional dynamic params ([#13725](https://github.com/remix-run/react-router/pull/13725))\n\n 7.6.1 introduced fixes for `href` when using optional static segments,\n but those fixes caused regressions with how optional dynamic params worked in 7.6.0:\n\n ```ts\n // 7.6.0\n href(\"/users/:id?\"); // โœ…\n href(\"/users/:id?\", { id: 1 }); // โœ…\n\n // 7.6.1\n href(\"/users/:id?\"); // โŒ\n href(\"/users/:id?\", { id: 1 }); // โŒ\n ```\n\n Now, optional static segments are expanded into different paths for `href`, but optional dynamic params are not.\n This way `href` can unambiguously refer to an exact URL path, all while keeping the number of path options to a minimum.\n\n ```ts\n // 7.6.2\n\n // path: /users/:id?/edit?\n href(\"\n // ^ suggestions when cursor is here:\n //\n // /users/:id?\n // /users/:id?/edit\n ```\n\n Additionally, you can pass `params` from component props without needing to narrow them manually:\n\n ```ts\n declare const params: { id?: number };\n\n // 7.6.0\n href(\"/users/:id?\", params);\n\n // 7.6.1\n href(\"/users/:id?\", params); // โŒ\n \"id\" in params ? href(\"/users/:id\", params) : href(\"/users\"); // works... but is annoying\n\n // 7.6.2\n href(\"/users/:id?\", params); // restores behavior of 7.6.0\n ```\n\n**Full Changelog**: [`v7.6.1...v7.6.2`](https://github.com/remix-run/react-router/compare/react-router@7.6.1...react-router@7.6.2)\n\n## v7.6.1\n\nDate: 2025-05-25\n\n### Patch Changes\n\n- `react-router` - Partially revert optimization added in `7.1.4` to reduce calls to `matchRoutes` because it surfaced other issues ([#13562](https://github.com/remix-run/react-router/pull/13562))\n- `react-router` - Update `Route.MetaArgs` to reflect that `data` can be potentially `undefined` ([#13563](https://github.com/remix-run/react-router/pull/13563))\n - This is primarily for cases where a route `loader` threw an error to it's own `ErrorBoundary`, but it also arises in the case of a 404 which renders the root `ErrorBoundary`/`meta` but the root `loader` did not run because not routes matched\n- `react-router` - Avoid initial fetcher execution 404 error when Lazy Route Discovery is interrupted by a navigation ([#13564](https://github.com/remix-run/react-router/pull/13564))\n- `react-router` - Properly `href` replaces splats `*` ([#13593](https://github.com/remix-run/react-router/pull/13593))\n - `href(\"/products/*\", { \"*\": \"/1/edit\" }); // -> /products/1/edit`\n- `@react-router/architect` - Update `@architect/functions` from `^5.2.0` to `^7.0.0` ([#13556](https://github.com/remix-run/react-router/pull/13556))\n- `@react-router/dev` - Prevent typegen with route files that are outside the `app/` directory ([#12996](https://github.com/remix-run/react-router/pull/12996))\n- `@react-router/dev` - Add additional logging to `build` command output when cleaning assets from server build ([#13547](https://github.com/remix-run/react-router/pull/13547))\n- `@react-router/dev` - Don't clean assets from server build when `build.ssrEmitAssets` has been enabled in Vite config ([#13547](https://github.com/remix-run/react-router/pull/13547))\n- `@react-router/dev` - Fix typegen when same route is used at multiple paths ([#13574](https://github.com/remix-run/react-router/pull/13574))\n - For example, `routes/route.tsx` is used at 4 different paths here:\n\n ```ts\n import { type RouteConfig, route } from \"@react-router/dev/routes\";\n export default [\n route(\"base/:base\", \"routes/base.tsx\", [\n route(\"home/:home\", \"routes/route.tsx\", { id: \"home\" }),\n route(\"changelog/:changelog\", \"routes/route.tsx\", { id: \"changelog\" }),\n route(\"splat/*\", \"routes/route.tsx\", { id: \"splat\" }),\n ]),\n route(\"other/:other\", \"routes/route.tsx\", { id: \"other\" }),\n ] satisfies RouteConfig;\n ```\n\n - Previously, typegen would arbitrarily pick one of these paths to be the \"winner\" and generate types for the route module based on that path\n - Now, typegen creates unions as necessary for alternate paths for the same route file\n\n- `@react-router/dev` - Better types for `params` ([#13543](https://github.com/remix-run/react-router/pull/13543))\n - For example:\n\n ```ts\n // routes.ts\n import { type RouteConfig, route } from \"@react-router/dev/routes\";\n\n export default [\n route(\"parent/:p\", \"routes/parent.tsx\", [\n route(\"route/:r\", \"routes/route.tsx\", [\n route(\"child1/:c1a/:c1b\", \"routes/child1.tsx\"),\n route(\"child2/:c2a/:c2b\", \"routes/child2.tsx\"),\n ]),\n ]),\n ] satisfies RouteConfig;\n ```\n\n - Previously, `params` for `routes/route` were calculated as `{ p: string, r: string }`.\n - This incorrectly ignores params that could come from child routes\n - If visiting `/parent/1/route/2/child1/3/4`, the actual params passed to `routes/route` will have a type of `{ p: string, r: string, c1a: string, c1b: string }`\n - Now, `params` are aware of child routes and autocompletion will include child params as optionals:\n\n ```ts\n params.|\n // ^ cursor is here and you ask for autocompletion\n // p: string\n // r: string\n // c1a?: string\n // c1b?: string\n // c2a?: string\n // c2b?: string\n ```\n\n - You can also narrow the types for `params` as it is implemented as a normalized union of params for each page that includes `routes/route`:\n\n ```ts\n if (typeof params.c1a === 'string') {\n params.|\n // ^ cursor is here and you ask for autocompletion\n // p: string\n // r: string\n // c1a: string\n // c1b: string\n }\n ```\n\n- `@react-router/dev` - Fix `href` for optional segments ([#13595](https://github.com/remix-run/react-router/pull/13595))\n - Type generation now expands paths with optionals into their corresponding non-optional paths\n - For example, the path `/user/:id?` gets expanded into `/user` and `/user/:id` to more closely model visitable URLs\n - `href` then uses these expanded (non-optional) paths to construct type-safe paths for your app:\n\n ```ts\n // original: /user/:id?\n // expanded: /user & /user/:id\n href(\"/user\"); // โœ…\n href(\"/user/:id\", { id: 1 }); // โœ…\n ```\n\n - This becomes even more important for static optional paths where there wasn't a good way to indicate whether the optional should be included in the resulting path:\n\n ```ts\n // original: /products/:id/detail?\n\n // before\n href(\"/products/:id/detail?\"); // โŒ How can we tell `href` to include or omit `detail?` segment with a complex API?\n\n // now\n // expanded: /products/:id & /products/:id/detail\n href(\"/product/:id\"); // โœ…\n href(\"/product/:id/detail\"); // โœ…\n ```\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `@react-router/dev` - Renamed internal `react-router/route-module` export to `react-router/internal` ([#13543](https://github.com/remix-run/react-router/pull/13543))\n- `@react-router/dev` - Removed `Info` export from generated `+types/*` files ([#13543](https://github.com/remix-run/react-router/pull/13543))\n- `@react-router/dev` - Normalize dirent entry path across node versions when generating SRI manifest ([#13591](https://github.com/remix-run/react-router/pull/13591))\n\n**Full Changelog**: [`v7.6.0...v7.6.1`](https://github.com/remix-run/react-router/compare/react-router@7.6.0...react-router@7.6.1)\n\n## v7.6.0\n\nDate: 2025-05-08\n\n### What's Changed\n\n#### `routeDiscovery` Config Option\n\nWe've added a new config option in `7.6.0` which grants you more control over the Lazy Route Discovery feature. You can now configure the `/__manifest` path if you're running multiple RR applications on the same server, or you can also disable the feature entirely if your application is small enough and the feature isn't necessary.\n\n```ts\n// react-router.config.ts\n\nexport default {\n // You can modify the manifest path used:\n routeDiscovery: { mode: \"lazy\", manifestPath: \"/custom-manifest\" }\n\n // Or you can disable this feature entirely and include all routes in the\n // manifest on initial document load:\n routeDiscovery: { mode: \"initial\" }\n\n // If you don't specify anything, the default config is as follows, which enables\n // Lazy Route Discovery and makes manifest requests to the `/__manifest` path:\n // routeDiscovery: { mode: \"lazy\", manifestPath: \"/__manifest\" }\n} satisfies Config;\n```\n\n#### Automatic Types for Future Flags\n\nSome future flags alter the way types should work in React Router. Previously, you had to remember to manually opt-in to the new types. For example, for `future.unstable_middleware`:\n\n```ts\n// react-router.config.ts\n\n// Step 1: Enable middleware\nexport default {\n future: {\n unstable_middleware: true,\n },\n};\n\n// Step 2: Enable middleware types\ndeclare module \"react-router\" {\n interface Future {\n unstable_middleware: true; // ๐Ÿ‘ˆ Enable middleware types\n }\n}\n```\n\nIt was up to you to keep the runtime future flags synced with the types for those flags. This was confusing and error-prone.\n\nNow, React Router will automatically enable types for future flags. That means you only need to specify the runtime future flag:\n\n```ts\n// react-router.config.ts\n\n// Step 1: Enable middleware\nexport default {\n future: {\n unstable_middleware: true,\n },\n};\n\n// No step 2! That's it!\n```\n\nBehind the scenes, React Router will generate the corresponding `declare module` into `.react-router/types`. Currently this is done in `.react-router/types/+register.ts` but this is an implementation detail that may change in the future.\n\n### Minor Changes\n\n- `react-router` - Added a new `routeDiscovery` option in `react-router.config.ts` to configure Lazy Route Discovery behavior ([#13451](https://github.com/remix-run/react-router/pull/13451))\n- `react-router` - Add support for route component props in `createRoutesStub` ([#13528](https://github.com/remix-run/react-router/pull/13528))\n - This allows you to unit test your route components using the props instead of the hooks:\n\n ```tsx\n let RoutesStub = createRoutesStub([\n {\n path: \"/\",\n Component({ loaderData }) {\n let data = loaderData as { message: string };\n return 
Message: {data.message}
;\n },\n loader() {\n return { message: \"hello\" };\n },\n },\n ]);\n\n render();\n\n await waitFor(() => screen.findByText(\"Message: hello\"));\n ```\n\n- `@react-router/dev` - Automatic types for future flags ([#13506](https://github.com/remix-run/react-router/pull/13506))\n\n### Patch Changes\n\nYou may notice this list is a bit larger than usual! The team ate their vegetables last week and spent the week [squashing bugs](https://x.com/BrooksLybrand/status/1918406062920589731) to work on lowering the issue count that had ballooned a bit since the v7 release.\n\n- `react-router` - Fix `react-router` module augmentation for `NodeNext` ([#13498](https://github.com/remix-run/react-router/pull/13498))\n- `react-router` - Don't bundle `react-router` in `react-router/dom` CJS export ([#13497](https://github.com/remix-run/react-router/pull/13497))\n- `react-router` - Fix bug where a submitting `fetcher` would get stuck in a `loading` state if a revalidating `loader` redirected ([#12873](https://github.com/remix-run/react-router/pull/12873))\n- `react-router` - Fix hydration error if a server `loader` returned `undefined` ([#13496](https://github.com/remix-run/react-router/pull/13496))\n- `react-router` - Fix initial load 404 scenarios in data mode ([#13500](https://github.com/remix-run/react-router/pull/13500))\n- `react-router` - Stabilize `useRevalidator`'s `revalidate` function ([#13542](https://github.com/remix-run/react-router/pull/13542))\n- `react-router` - Preserve status code if a `clientAction` throws a `data()` result in framework mode ([#13522](https://github.com/remix-run/react-router/pull/13522))\n- `react-router` - Be defensive against leading double slashes in paths to avoid `Invalid URL` errors from the URL constructor ([#13510](https://github.com/remix-run/react-router/pull/13510))\n - Note we do not sanitize/normalize these paths - we only detect them so we can avoid the error that would be thrown by `new URL(\"//\", window.location.origin)`\n- `react-router` - Remove `Navigator` declaration for `navigator.connection.saveData` to avoid messing with any other types beyond `saveData` in user land ([#13512](https://github.com/remix-run/react-router/pull/13512))\n- `react-router` - Fix `handleError` `params` values on `.data` requests for routes with a dynamic param as the last URL segment ([#13481](https://github.com/remix-run/react-router/pull/13481))\n- `react-router` - Don't trigger an `ErrorBoundary` UI before the reload when we detect a manifest version mismatch in Lazy Route Discovery ([#13480](https://github.com/remix-run/react-router/pull/13480))\n- `react-router` - Inline `turbo-stream@2.4.1` dependency and fix decoding ordering of `Map`/`Set` instances ([#13518](https://github.com/remix-run/react-router/pull/13518))\n- `react-router` - Only render dev warnings during dev ([#13461](https://github.com/remix-run/react-router/pull/13461))\n- `react-router` - Short circuit post-processing on aborted `dataStrategy` requests ([#13521](https://github.com/remix-run/react-router/pull/13521))\n - This resolves non-user-facing console errors of the form `Cannot read properties of undefined (reading 'result')`\n- `@react-router/dev` - Support project root directories without a `package.json` if it exists in a parent directory ([#13472](https://github.com/remix-run/react-router/pull/13472))\n- `@react-router/dev` - When providing a custom Vite config path via the CLI `--config`/`-c` flag, default the project root directory to the directory containing the Vite config when not explicitly provided ([#13472](https://github.com/remix-run/react-router/pull/13472))\n- `@react-router/dev` - In a `routes.ts` context, ensure the `--mode` flag is respected for `import.meta.env.MODE` ([#13485](https://github.com/remix-run/react-router/pull/13485))\n - Previously, `import.meta.env.MODE` within a `routes.ts` context was always `\"development\"` for the `dev` and `typegen --watch` commands, but otherwise resolved to `\"production\"`. These defaults are still in place, but if a `--mode` flag is provided, this will now take precedence.\n- `@react-router/dev` - Ensure consistent project root directory resolution logic in CLI commands ([#13472](https://github.com/remix-run/react-router/pull/13472))\n- `@react-router/dev` - When executing `react-router.config.ts` and `routes.ts` with `vite-node`, ensure that PostCSS config files are ignored ([#13489](https://github.com/remix-run/react-router/pull/13489))\n- `@react-router/dev` - When extracting critical CSS during development, ensure it's loaded from the client environment to avoid issues with plugins that handle the SSR environment differently ([#13503](https://github.com/remix-run/react-router/pull/13503))\n- `@react-router/dev` - Fix \"Status message is not supported by HTTP/2\" error during dev when using HTTPS ([#13460](https://github.com/remix-run/react-router/pull/13460))\n- `@react-router/dev` - Update config when `react-router.config.ts` is created or deleted during development ([#12319](https://github.com/remix-run/react-router/pull/12319))\n- `@react-router/dev` - Skip unnecessary `routes.ts` evaluation before Vite build is started ([#13513](https://github.com/remix-run/react-router/pull/13513))\n- `@react-router/dev` - Fix `TS2300: Duplicate identifier` errors caused by generated types ([#13499](https://github.com/remix-run/react-router/pull/13499))\n- Previously, routes that had the same full path would cause duplicate entries in the generated types for `href` (`.react-router/types/+register.ts`), causing type checking errors\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `react-router` - Fix a few bugs with error bubbling in middleware use-cases ([#13538](https://github.com/remix-run/react-router/pull/13538))\n- `@react-router/dev` - When `future.unstable_viteEnvironmentApi` is enabled, ensure that `build.assetsDir` in Vite config is respected when `environments.client.build.assetsDir` is not configured ([#13491](https://github.com/remix-run/react-router/pull/13491))\n\n### Changes by Package\n\n- [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/create-react-router/CHANGELOG.md#760)\n- [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router/CHANGELOG.md#760)\n- [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-architect/CHANGELOG.md#760)\n- [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-cloudflare/CHANGELOG.md#760)\n- [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-dev/CHANGELOG.md#760)\n- [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-express/CHANGELOG.md#760)\n- [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-fs-routes/CHANGELOG.md#760)\n- [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-node/CHANGELOG.md#760)\n- [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#760)\n- [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-serve/CHANGELOG.md#760)\n\n**Full Changelog**: [`v7.5.3...v7.6.0`](https://github.com/remix-run/react-router/compare/react-router@7.5.3...react-router@7.6.0)\n\n## v7.5.3\n\nDate: 2025-04-28\n\n### Patch Changes\n\n- `react-router` - Fix bug where bubbled action errors would result in `loaderData` being cleared at the handling `ErrorBoundary` route ([#13476](https://github.com/remix-run/react-router/pull/13476))\n- `react-router` - Handle redirects from `clientLoader.hydrate` initial load executions ([#13477](https://github.com/remix-run/react-router/pull/13477))\n\n**Full Changelog**: [`v7.5.2...v7.5.3`](https://github.com/remix-run/react-router/compare/react-router@7.5.2...react-router@7.5.3)\n\n## v7.5.2\n\nDate: 2025-04-24\n\n### Security Notice\n\nFixed 2 security vulnerabilities that could result in cache-poisoning attacks by sending specific headers intended for build-time usage for SPA Mode and Pre-rendering ([GHSA-f46r-rw29-r322](https://github.com/remix-run/react-router/security/advisories/GHSA-f46r-rw29-r322), [GHSA-cpj6-fhp6-mr6j](https://github.com/remix-run/react-router/security/advisories/GHSA-cpj6-fhp6-mr6j)).\n\n### Patch Changes\n\n- `react-router` - Adjust approach for Pre-rendering/SPA Mode via headers ([#13453](https://github.com/remix-run/react-router/pull/13453))\n- `react-router` - Update Single Fetch to also handle the 204 redirects used in `?_data` requests in Remix v2 ([#13364](https://github.com/remix-run/react-router/pull/13364))\n - This allows applications to trigger a redirect on `.data` requests from outside the scope of React Router (i.e., an `express`/`hono` middleware) the same way they did in Remix v2 before Single Fetch was implemented\n - This is a bit of an escape hatch - the recommended way to handle this is redirecting from a root route middleware\n - To use this functionality, you may return from a `.data` request wih a response as follows:\n - Set a 204 status code\n - Set an `X-Remix-Redirect: ` header\n - Optionally, set `X-Remix-Replace: true` or `X-Remix-Reload-Document: true` headers to replicate `replace()`/`redirectDocument()` functionality\n - โš ๏ธ Please note that these responses rely on implementation details that are subject to change without a SemVer major release, and it is recommended you set up integration tests for your application to confirm this functionality is working correctly with each future React Router upgrade\n\n**Full Changelog**: [`v7.5.1...v7.5.2`](https://github.com/remix-run/react-router/compare/react-router@7.5.1...react-router@7.5.2)\n\n## v7.5.1\n\nDate: 2025-04-17\n\n### Patch Changes\n\n- `react-router` - When using the object-based `route.lazy` API, the `HydrateFallback` and `hydrateFallbackElement` properties are now skipped when lazy loading routes after hydration ([#13376](https://github.com/remix-run/react-router/pull/13376))\n - If you move the code for these properties into a separate file, since the hydrate properties were unused already (if the route wasn't present during hydration), you can avoid downloading them at all. For example:\n\n ```ts\n createBrowserRouter([\n {\n path: \"/show/:showId\",\n lazy: {\n loader: async () => (await import(\"./show.loader.js\")).loader,\n Component: async () =>\n (await import(\"./show.component.js\")).Component,\n HydrateFallback: async () =>\n (await import(\"./show.hydrate-fallback.js\")).HydrateFallback,\n },\n },\n ]);\n ```\n\n- `react-router` - Fix single fetch bug where no revalidation request would be made when navigating upwards to a reused parent route ([#13253](https://github.com/remix-run/react-router/pull/13253))\n- `react-router` - Properly revalidate pre-rendered paths when param values change when using `ssr:false` + `prerender` configs ([#13380](https://github.com/remix-run/react-router/pull/13380))\n- `react-router` - Fix pre-rendering when a loader returns a redirect ([#13365](https://github.com/remix-run/react-router/pull/13365))\n- `react-router` - Do not automatically add `null` to `staticHandler.query()` `context.loaderData` if routes do not have loaders ([#13223](https://github.com/remix-run/react-router/pull/13223))\n - This was a Remix v2 implementation detail inadvertently left in for React Router v7\n - Now that we allow returning `undefined` from loaders, our prior check of `loaderData[routeId] !== undefined` was no longer sufficient and was changed to a `routeId in loaderData` check - these `null` values can cause issues for this new check\n - โš ๏ธ This could be a \"breaking bug fix\" for you if you are doing manual SSR with `createStaticHandler()`/``, and using `context.loaderData` to control `` hydration behavior on the client\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `react-router` - Add better error messaging when `getLoadContext` is not updated to return a `Map` ([#13242](https://github.com/remix-run/react-router/pull/13242))\n- `react-router` - Update context type for `LoaderFunctionArgs`/`ActionFunctionArgs` when middleware is enabled ([#13381](https://github.com/remix-run/react-router/pull/13381))\n- `react-router` - Add a new `unstable_runClientMiddleware` argument to `dataStrategy` to enable middleware execution in custom `dataStrategy` implementations ([#13395](https://github.com/remix-run/react-router/pull/13395))\n- `react-router` - Add support for the new `unstable_shouldCallHandler`/`unstable_shouldRevalidateArgs` APIs in `dataStrategy` ([#13253](https://github.com/remix-run/react-router/pull/13253))\n\n**Full Changelog**: [`v7.5.0...v7.5.1`](https://github.com/remix-run/react-router/compare/react-router@7.5.0...react-router@7.5.1)\n\n## v7.5.0\n\nDate: 2025-04-04\n\n### What's Changed\n\n#### `route.lazy` Object API\n\nWe've introduced a new `route.lazy` API which gives you more granular control over the lazy loading of route properties that you could not achieve with the `route.lazy()` function signature. This is useful for Framework mode and performance-critical library mode applications.\n\n```ts\ncreateBrowserRouter([\n {\n path: \"/show/:showId\",\n lazy: {\n loader: async () => (await import(\"./show.loader.js\")).loader,\n action: async () => (await import(\"./show.action.js\")).action,\n Component: async () => (await import(\"./show.component.js\")).Component,\n },\n },\n]);\n```\n\nโš ๏ธ This is a breaking change if you have adopted the `route.unstable_lazyMiddleware` API which has been removed in favor of `route.lazy.unstable_middleware`. See the `Unstable Changes` section below for more information.\n\n### Minor Changes\n\n- `react-router` - Add granular object-based API for `route.lazy` to support lazy loading of individual route properties ([#13294](https://github.com/remix-run/react-router/pull/13294))\n\n### Patch Changes\n\n- `@react-router/dev` - Update optional `wrangler` peer dependency range to support `wrangler` v4 ([#13258](https://github.com/remix-run/react-router/pull/13258))\n- `@react-router/dev` - Reinstate dependency optimization in the child compiler to fix `depsOptimizer is required in dev mode` errors when using `vite-plugin-cloudflare` and importing Node.js builtins ([#13317](https://github.com/remix-run/react-router/pull/13317))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `react-router` - Introduce `future.unstable_subResourceIntegrity` flag that enables generation of an `importmap` with `integrity` for the scripts that will be loaded by the browser ([#13163](https://github.com/remix-run/react-router/pull/13163))\n- `react-router` - Remove support for the `route.unstable_lazyMiddleware` property ([#13294](https://github.com/remix-run/react-router/pull/13294))\n - In order to lazily load middleware, you can use the new object-based `route.lazy.unstable_middleware` API\n- `@react-router/dev` - When `future.unstable_viteEnvironmentApi` is enabled, ensure critical CSS in development works when using a custom Vite `base` has been configured ([#13305](https://github.com/remix-run/react-router/pull/13305))\n\n### Changes by Package\n\n- [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/create-react-router/CHANGELOG.md#750)\n- [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router/CHANGELOG.md#750)\n- [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-architect/CHANGELOG.md#750)\n- [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-cloudflare/CHANGELOG.md#750)\n- [`@react-router/dev`](http://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-dev/CHANGELOG.md#750)\n- [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-express/CHANGELOG.md#750)\n- [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-fs-routes/CHANGELOG.md#750)\n- [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-node/CHANGELOG.md#750)\n- [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#750)\n- [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-serve/CHANGELOG.md#750)\n\n**Full Changelog**: [`v7.4.1...v7.5.0`](https://github.com/remix-run/react-router/compare/react-router@7.4.1...react-router@7.5.0)\n\n## v7.4.1\n\nDate: 2025-03-28\n\n### Security Notice\n\nFixed a security vulnerability that allowed URL manipulation and potential cache pollution via the `Host` and `X-Forwarded-Host` headers due to inadequate port sanitization ([GHSA-4q56-crqp-v477/CVE-2025-31137](https://github.com/remix-run/react-router/security/advisories/GHSA-4q56-crqp-v477)).\n\n### Patch Changes\n\n- `react-router` - Dedupe calls to `route.lazy` functions ([#13260](https://github.com/remix-run/react-router/pull/13260))\n- `@react-router/dev` - Fix path in prerender error messages ([#13257](https://github.com/remix-run/react-router/pull/13257))\n- `@react-router/dev` - Fix typegen for virtual modules when `moduleDetection` is set to `force` ([#13267](https://github.com/remix-run/react-router/pull/13267))\n- `@react-router/express` - Better validation of `x-forwarded-host` header to prevent potential security issues ([#13309](https://github.com/remix-run/react-router/pull/13309))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `react-router` - Fix types on `unstable_MiddlewareFunction` to avoid type errors when a middleware doesn't return a value ([#13311](https://github.com/remix-run/react-router/pull/13311))\n- `react-router` - Add support for `route.unstable_lazyMiddleware` function to allow lazy loading of middleware logic ([#13210](https://github.com/remix-run/react-router/pull/13210))\n - โš ๏ธ We do not recommend adoption of this API currently as we are likely going to change it prior to the stable release of middleware\n - โš ๏ธ This may be a breaking change if your app is currently returning `unstable_middleware` from `route.lazy`\n - The `route.unstable_middleware` property is no longer supported in the return value from `route.lazy`\n - If you want to lazily load middleware, you must use `route.unstable_lazyMiddleware`\n- `@react-router/dev` - When both `future.unstable_middleware` and `future.unstable_splitRouteModules` are enabled, split `unstable_clientMiddleware` route exports into separate chunks when possible ([#13210](https://github.com/remix-run/react-router/pull/13210))\n- `@react-router/dev` - Improve performance of `future.unstable_middleware` by ensuring that route modules are only blocking during the middleware phase when the `unstable_clientMiddleware` has been defined ([#13210](https://github.com/remix-run/react-router/pull/13210))\n\n**Full Changelog**: [`v7.4.0...v7.4.1`](https://github.com/remix-run/react-router/compare/react-router@7.4.0...react-router@7.4.1)\n\n## v7.4.0\n\nDate: 2025-03-19\n\n### Minor Changes\n\n- `@react-router/dev` - Generate types for `virtual:react-router/server-build` module ([#13152](https://github.com/remix-run/react-router/pull/13152))\n\n### Patch Changes\n\n- `react-router` - Fix root loader data on initial load redirects in SPA mode ([#13222](https://github.com/remix-run/react-router/pull/13222))\n- `react-router` - Load ancestor pathless/index routes in lazy route discovery for upwards non-eager-discovery routing ([#13203](https://github.com/remix-run/react-router/pull/13203))\n- `react-router` - Fix `shouldRevalidate` behavior for `clientLoader`-only routes in `ssr:true` apps ([#13221](https://github.com/remix-run/react-router/pull/13221))\n- `@react-router/dev` - Fix conflicts with other Vite plugins that use the `configureServer` and/or `configurePreviewServer` hooks ([#13184](https://github.com/remix-run/react-router/pull/13184))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `react-router` - If a middleware throws an error, ensure we only bubble the error itself via `next()` and are no longer leaking the `MiddlewareError` implementation detail ([#13180](https://github.com/remix-run/react-router/pull/13180))\n - โš ๏ธ This may be a breaking change if you are `catch`-ing errors thrown by the `next()` function in your middlewares\n- `react-router` - Fix `RequestHandler` `loadContext` parameter type when middleware is enabled ([#13204](https://github.com/remix-run/react-router/pull/13204))\n- `react-router` - Update `Route.unstable_MiddlewareFunction` to have a return value of `Response | undefined` instead of `Response | void` ([#13199](https://github.com/remix-run/react-router/pull/13199))\n- `@react-router/dev` - When `future.unstable_splitRouteModules` is set to `\"enforce\"`, allow both splittable and unsplittable root route exports since it's always in a single chunk ([#13238](https://github.com/remix-run/react-router/pull/13238))\n- `@react-router/dev` - When `future.unstable_viteEnvironmentApi` is enabled, allow plugins that override the default SSR environment (such as `@cloudflare/vite-plugin`) to be placed before or after the React Router plugin ([#13183](https://github.com/remix-run/react-router/pull/13183))\n\n### Changes by Package\n\n- [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/create-react-router/CHANGELOG.md#740)\n- [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router/CHANGELOG.md#740)\n- [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-architect/CHANGELOG.md#740)\n- [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-cloudflare/CHANGELOG.md#740)\n- [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-dev/CHANGELOG.md#740)\n- [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-express/CHANGELOG.md#740)\n- [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-fs-routes/CHANGELOG.md#740)\n- [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-node/CHANGELOG.md#740)\n- [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#740)\n- [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-serve/CHANGELOG.md#740)\n\n**Full Changelog**: [`v7.3.0...v7.4.0`](https://github.com/remix-run/react-router/compare/react-router@7.3.0...react-router@7.4.0)\n\n## v7.3.0\n\nDate: 2025-03-06\n\n### Minor Changes\n\n- Add `fetcherKey` as a parameter to `patchRoutesOnNavigation` ([#13061](https://github.com/remix-run/react-router/pull/13061))\n\n### Patch Changes\n\n- `react-router` - Detect and handle manifest-skew issues on new deploys during active sessions ([#13061](https://github.com/remix-run/react-router/pull/13061))\n - In framework mode, Lazy Route Discovery will now detect manifest version mismatches in active sessions after a new deploy\n - On navigations to undiscovered routes, this mismatch will trigger a document reload of the destination path\n - On `fetcher` calls to undiscovered routes, this mismatch will trigger a document reload of the current path\n- `react-router` - Skip resource route flow in dev server in SPA mode ([#13113](https://github.com/remix-run/react-router/pull/13113))\n- `react-router` - Fix single fetch `_root.data` requests when a `basename` is used ([#12898](https://github.com/remix-run/react-router/pull/12898))\n- `react-router` - Fix types for `loaderData` and `actionData` that contained `Record`s ([#13139](https://github.com/remix-run/react-router/pull/13139))\n - โš ๏ธ This is a breaking change for users who have already adopted `unstable_SerializesTo` - see the note in the `Unstable Changes` section below for more information\n- `@react-router/dev` - Fix support for custom client `build.rollupOptions.output.entryFileNames` ([#13098](https://github.com/remix-run/react-router/pull/13098))\n- `@react-router/dev` - Fix usage of `prerender` option when `serverBundles` option has been configured or provided by a preset, e.g. `vercelPreset` from `@vercel/react-router` ([#13082](https://github.com/remix-run/react-router/pull/13082))\n- `@react-router/dev` - Fix support for custom `build.assetsDir` ([#13077](https://github.com/remix-run/react-router/pull/13077))\n- `@react-router/dev` - Remove unused dependencies ([#13134](https://github.com/remix-run/react-router/pull/13134))\n- `@react-router/dev` - Stub all routes except root in \"SPA Mode\" server builds to avoid issues when route modules or their dependencies import non-SSR-friendly modules ([#13023](https://github.com/remix-run/react-router/pull/13023))\n- `@react-router/dev` - Remove unused Vite file system watcher ([#13133](https://github.com/remix-run/react-router/pull/13133))\n- `@react-router/dev` - Fix support for custom SSR build input when `serverBundles` option has been configured ([#13107](https://github.com/remix-run/react-router/pull/13107))\n - โš ๏ธ Note that for consumers using the `future.unstable_viteEnvironmentApi` and `serverBundles` options together, hyphens are no longer supported in server bundle IDs since they also need to be valid Vite environment names.\n- `@react-router/dev` - Fix dev server when using HTTPS by stripping HTTP/2 pseudo headers from dev server requests ([#12830](https://github.com/remix-run/react-router/pull/12830))\n- `@react-router/dev` - Lazy load Cloudflare platform proxy on first dev server request when using the `cloudflareDevProxy` Vite plugin to avoid creating unnecessary `workerd` processes ([#13016](https://github.com/remix-run/react-router/pull/13016))\n- `@react-router/dev` - Fix duplicated entries in typegen for layout routes and their corresponding index route ([#13140](https://github.com/remix-run/react-router/pull/13140))\n- `@react-router/express` - Update `express` `peerDependency` to include v5 (https://github.com/remix-run/react-router/pull/13064) ([#12961](https://github.com/remix-run/react-router/pull/12961))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `react-router` - Add `context` support to client side data routers (unstable) ([#12941](https://github.com/remix-run/react-router/pull/12941))\n- `react-router` - Support middleware on routes (unstable) ([#12941](https://github.com/remix-run/react-router/pull/12941))\n- `@react-router/dev` - Fix errors with `future.unstable_viteEnvironmentApi` when the `ssr` environment has been configured by another plugin to be a custom `Vite.DevEnvironment` rather than the default `Vite.RunnableDevEnvironment` ([#13008](https://github.com/remix-run/react-router/pull/13008))\n- `@react-router/dev` - When `future.unstable_viteEnvironmentApi` is enabled and the `ssr` environment has `optimizeDeps.noDiscovery` disabled, define `optimizeDeps.entries` and `optimizeDeps.include` ([#13007](https://github.com/remix-run/react-router/pull/13007))\n\n#### Client-side `context` (unstable)\n\nYour application `clientLoader`/`clientAction` functions (or `loader`/`action` in library mode) will now receive a `context` parameter on the client. This is an instance of `unstable_RouterContextProvider` that you use with type-safe contexts (similar to `React.createContext`) and is most useful with the corresponding `unstable_clientMiddleware` API:\n\n```ts\nimport { unstable_createContext } from \"react-router\";\n\ntype User = {\n /*...*/\n};\n\nconst userContext = unstable_createContext();\n\nconst sessionMiddleware: Route.unstable_ClientMiddlewareFunction = async ({\n context,\n}) => {\n let user = await getUser();\n context.set(userContext, user);\n};\n\nexport const unstable_clientMiddleware = [sessionMiddleware];\n\nexport function clientLoader({ context }: Route.ClientLoaderArgs) {\n let user = context.get(userContext);\n let profile = await getProfile(user.id);\n return { profile };\n}\n```\n\nSimilar to server-side requests, a fresh `context` will be created per navigation (or `fetcher` call). If you have initial data you'd like to populate in the context for every request, you can provide an `unstable_getContext` function at the root of your app:\n\n- Library mode - `createBrowserRouter(routes, { unstable_getContext })`\n- Framework mode - ``\n\nThis function should return an value of type `unstable_InitialContext` which is a `Map` of context's and initial values:\n\n```ts\nconst loggerContext = unstable_createContext<(...args: unknown[]) => void>();\n\nfunction logger(...args: unknown[]) {\n console.log(new Date.toISOString(), ...args);\n}\n\nfunction unstable_getContext() {\n let map = new Map();\n map.set(loggerContext, logger);\n return map;\n}\n```\n\n#### Middleware (unstable)\n\nMiddleware is implemented behind a `future.unstable_middleware` flag. To enable, you must enable the flag and the types in your `react-router.config.ts` file:\n\n```ts\nimport type { Config } from \"@react-router/dev/config\";\nimport type { Future } from \"react-router\";\n\ndeclare module \"react-router\" {\n interface Future {\n unstable_middleware: true; // ๐Ÿ‘ˆ Enable middleware types\n }\n}\n\nexport default {\n future: {\n unstable_middleware: true, // ๐Ÿ‘ˆ Enable middleware\n },\n} satisfies Config;\n```\n\nโš ๏ธ Middleware is unstable and should not be adopted in production. There is at least one known de-optimization in route module loading for `clientMiddleware` that we will be addressing this before a stable release.\n\nโš ๏ธ Enabling middleware contains a breaking change to the `context` parameter passed to your `loader`/`action` functions - see below for more information.\n\nOnce enabled, routes can define an array of middleware functions that will run sequentially before route handlers run. These functions accept the same parameters as `loader`/`action` plus an additional `next` parameter to run the remaining data pipeline. This allows middlewares to perform logic before and after handlers execute.\n\n```tsx\n// Framework mode\nexport const unstable_middleware = [serverLogger, serverAuth]; // server\nexport const unstable_clientMiddleware = [clientLogger]; // client\n\n// Library mode\nconst routes = [\n {\n path: \"/\",\n // Middlewares are client-side for library mode SPA's\n unstable_middleware: [clientLogger, clientAuth],\n loader: rootLoader,\n Component: Root,\n },\n];\n```\n\nHere's a simple example of a client-side logging middleware that can be placed on the root route:\n\n```tsx\nconst clientLogger: Route.unstable_ClientMiddlewareFunction = async (\n { request },\n next,\n) => {\n let start = performance.now();\n\n // Run the remaining middlewares and all route loaders\n await next();\n\n let duration = performance.now() - start;\n console.log(`Navigated to ${request.url} (${duration}ms)`);\n};\n```\n\nNote that in the above example, the `next`/`middleware` functions don't return anything. This is by design as on the client there is no \"response\" to send over the network like there would be for middlewares running on the server. The data is all handled behind the scenes by the stateful `router`.\n\nFor a server-side middleware, the `next` function will return the HTTP `Response` that React Router will be sending across the wire, thus giving you a chance to make changes as needed. You may throw a new response to short circuit and respond immediately, or you may return a new or altered response to override the default returned by `next()`.\n\n```tsx\nconst serverLogger: Route.unstable_MiddlewareFunction = async (\n { request, params, context },\n next,\n) => {\n let start = performance.now();\n\n // ๐Ÿ‘‡ Grab the response here\n let res = await next();\n\n let duration = performance.now() - start;\n console.log(`Navigated to ${request.url} (${duration}ms)`);\n\n // ๐Ÿ‘‡ And return it here (optional if you don't modify the response)\n return res;\n};\n```\n\nYou can throw a `redirect` from a middleware to short circuit any remaining processing:\n\n```tsx\nimport { sessionContext } from \"../context\";\nconst serverAuth: Route.unstable_MiddlewareFunction = (\n { request, params, context },\n next,\n) => {\n let session = context.get(sessionContext);\n let user = session.get(\"user\");\n if (!user) {\n session.set(\"returnTo\", request.url);\n throw redirect(\"/login\", 302);\n }\n};\n```\n\n_Note that in cases like this where you don't need to do any post-processing you don't need to call the `next` function or return a `Response`._\n\nHere's another example of using a server middleware to detect 404s and check the CMS for a redirect:\n\n```tsx\nconst redirects: Route.unstable_MiddlewareFunction = async ({\n request,\n next,\n}) => {\n // attempt to handle the request\n let res = await next();\n\n // if it's a 404, check the CMS for a redirect, do it last\n // because it's expensive\n if (res.status === 404) {\n let cmsRedirect = await checkCMSRedirects(request.url);\n if (cmsRedirect) {\n throw redirect(cmsRedirect, 302);\n }\n }\n\n return res;\n};\n```\n\nFor more information on the `middleware` API/design, please see the [decision doc](https://github.com/remix-run/react-router/blob/release-next/decisions/0014-context-middleware.md).\n\n##### Middleware `context` parameter\n\nWhen middleware is enabled, your application will use a different type of `context` parameter in your loaders and actions to provide better type safety. Instead of `AppLoadContext`, `context` will now be an instance of `ContextProvider` that you can use with type-safe contexts (similar to `React.createContext`):\n\n```ts\nimport { unstable_createContext } from \"react-router\";\nimport { Route } from \"./+types/root\";\nimport type { Session } from \"./sessions.server\";\nimport { getSession } from \"./sessions.server\";\n\nlet sessionContext = unstable_createContext();\n\nconst sessionMiddleware: Route.unstable_MiddlewareFunction = ({\n context,\n request,\n}) => {\n let session = await getSession(request);\n context.set(sessionContext, session);\n // ^ must be of type Session\n};\n\n// ... then in some downstream middleware\nconst loggerMiddleware: Route.unstable_MiddlewareFunction = ({\n context,\n request,\n}) => {\n let session = context.get(sessionContext);\n // ^ typeof Session\n console.log(session.get(\"userId\"), request.method, request.url);\n};\n\n// ... or some downstream loader\nexport function loader({ context }: Route.LoaderArgs) {\n let session = context.get(sessionContext);\n let profile = await getProfile(session.get(\"userId\"));\n return { profile };\n}\n```\n\nIf you are using a custom server with a `getLoadContext` function, the return value for initial context values passed from the server adapter layer is no longer an object and should now return an `unstable_InitialContext` (`Map`):\n\n```ts\nlet adapterContext = unstable_createContext();\n\nfunction getLoadContext(req, res): unstable_InitialContext {\n let map = new Map();\n map.set(adapterContext, getAdapterContext(req));\n return map;\n}\n```\n\n#### `unstable_SerializesTo`\n\n`unstable_SerializesTo` added a way to register custom serialization types in Single Fetch for other library and framework authors like Apollo. It was implemented with branded type whose branded property that was made optional so that casting arbitrary values was easy:\n\n```ts\n// without the brand being marked as optional\nlet x1 = 42 as unknown as unstable_SerializesTo;\n// ^^^^^^^^^^\n\n// with the brand being marked as optional\nlet x2 = 42 as unstable_SerializesTo;\n```\n\nHowever, this broke type inference in `loaderData` and `actionData` for any `Record` types as those would now (incorrectly) match `unstable_SerializesTo`. This affected all users, not just those that depended on `unstable_SerializesTo`. To fix this, the branded property of `unstable_SerializesTo` is marked as required instead of optional.\n\nFor library and framework authors using `unstable_SerializesTo`, you may need to add `as unknown` casts before casting to `unstable_SerializesTo`.\n\n### Changes by Package\n\n- [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/create-react-router/CHANGELOG.md#730)\n- [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router/CHANGELOG.md#730)\n- [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-architect/CHANGELOG.md#730)\n- [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-cloudflare/CHANGELOG.md#730)\n- [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-dev/CHANGELOG.md#730)\n- [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-express/CHANGELOG.md#730)\n- [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-fs-routes/CHANGELOG.md#730)\n- [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-node/CHANGELOG.md#730)\n- [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#730)\n- [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-serve/CHANGELOG.md#730)\n\n**Full Changelog**: [`v7.2.0...v7.3.0`](https://github.com/remix-run/react-router/compare/react-router@7.2.0...react-router@7.3.0)\n\n## v7.2.0\n\nDate: 2025-02-18\n\n### What's Changed\n\n#### Type-safe `href` utility\n\nIn framework mode, we now provide you with a fully type-safe `href` utility to give you all the warm and fuzzy feelings of path auto-completion and param validation for links in your application:\n\n```tsx\nimport { href } from \"react-router\";\n\nexport default function Component() {\n const link = href(\"/blog/:slug\", { slug: \"my-first-post\" });\n // ^ type-safe! ^ Also type-safe!\n\n return (\n
\n \n \n
\n );\n}\n```\n\nYou'll now get type errors if you pass a bad path value or a bad param value:\n\n```ts\nconst badPath = href(\"/not/a/valid/path\");\n// ^ Error!\n\nconst badParam = href(\"/blog/:slug\", { oops: \"bad param\" });\n// ^ Error!\n```\n\n#### Prerendering with a SPA Fallback\n\nThis release enhances the ability to use a combination of pre-rendered paths alongside other paths that operate in \"SPA Mode\" when pre-rendering with `ssr:false`.\n\n- If you specify `ssr:false` without a `prerender` config, this is considered \"SPA Mode\" and the generated `index.html` file will only render down to the root route and will be able to hydrate for any valid application path\n- If you specify `ssr:false` with a `prerender` config but _do not_ include the `/` path (i.e., `prerender: ['/blog/post']`), then we still generate a \"SPA Mode\" `index.html` file that can hydrate for any path in the application\n- If you specify `ssr:false` and include the `/` path in your `prerender` config, the generated `index.html` file will be specific to the root index route, so we will now also generate a separate \"SPA Mode\" file in `__spa-fallback.html` that you can serve/hydrate for non-prerendered paths\n\nFor more info, see the [Pre-rendering](https://reactrouter.com/dev/how-to/pre-rendering#pre-rendering-with-a-spa-fallback) docs for more info.\n\n#### Allow a root `loader` in SPA Mode\n\nSPA Mode used to prohibit the use of loaders in all routes so that we could hydrate for any path in the application. However, because the root route is always rendered at build time, we can lift this restriction for the root route.\n\nIn order to use your build-time loader data during pre-rendering, we now also expose the `loaderData` as an optional prop for the `HydrateFallback` component on routes:\n\n- This will be defined so long as the `HydrateFallback` is rendering because _children_ routes are loading\n- This will be `undefined` if the `HydrateFallback` is rendering because the route itself has it's own hydrating `clientLoader`\n - In SPA mode, this will allow you to render loader root data into the SPA Mode HTML file\n\n### Minor Changes\n\n- `react-router` - New type-safe `href` utility that guarantees links point to actual paths in your app ([#13012](https://github.com/remix-run/react-router/pull/13012))\n- `@react-router/dev` - Generate a \"SPA fallback\" HTML file when pre-rendering the `/` route with `ssr:false` ([#12948](https://github.com/remix-run/react-router/pull/12948))\n- `@react-router/dev` - Allow a `loader` in the root route in SPA mode because it can be called/server-rendered at build time ([#12948](https://github.com/remix-run/react-router/pull/12948))\n - `Route.HydrateFallbackProps` now also receives `loaderData`\n\n### Patch Changes\n\n- `react-router` - Disable Lazy Route Discovery for all `ssr:false` apps and not just \"SPA Mode\" because there is no runtime server to serve the search-param-configured `__manifest` requests ([#12894](https://github.com/remix-run/react-router/pull/12894))\n - We previously only disabled this for \"SPA Mode\" but we realized it should apply to all `ssr:false` apps\n - In those `prerender` scenarios we would pre-render the `/__manifest` file but that makes some unnecessary assumptions about the static file server behaviors\n- `react-router` - Don't apply Single Fetch revalidation de-optimization when in SPA mode since there is no server HTTP request ([#12948](https://github.com/remix-run/react-router/pull/12948))\n- `react-router` - Properly handle revalidations to across a pre-render/SPA boundary ([#13021](https://github.com/remix-run/react-router/pull/13021))\n - In \"hybrid\" applications where some routes are pre-rendered and some are served from a SPA fallback, we need to avoid making `.data` requests if the path wasn't pre-rendered because the request will 404\n - We don't know all the pre-rendered paths client-side, however:\n - All `loader` data in `ssr:false` mode is static because it's generated at build time\n - A route must use a `clientLoader` to do anything dynamic\n - Therefore, if a route only has a `loader` and not a `clientLoader`, we disable revalidation by default because there is no new data to retrieve\n - We short circuit and skip single fetch `.data` request logic if there are no server loaders with `shouldLoad=true` in our single fetch `dataStrategy`\n - This ensures that the route doesn't cause a `.data` request that would 404 after a submission\n- `react-router` - Align dev server behavior with static file server behavior when `ssr:false` is set ([#12948](https://github.com/remix-run/react-router/pull/12948))\n - When no `prerender` config exists, only SSR down to the root `HydrateFallback` (SPA Mode)\n - When a `prerender` config exists but the current path is not pre-rendered, only SSR down to the root `HydrateFallback` (SPA Fallback)\n - Return a 404 on `.data` requests to non-pre-rendered paths\n- `react-router` - Improve prefetch performance of CSS side effects in framework mode ([#12889](https://github.com/remix-run/react-router/pull/12889))\n- `react-router` - Properly handle interrupted manifest requests in lazy route discovery ([#12915](https://github.com/remix-run/react-router/pull/12915))\n- `@react-router/dev` - Handle custom `envDir` in Vite config ([#12969](https://github.com/remix-run/react-router/pull/12969))\n- `@react-router/dev` - Fix CLI parsing to allow argument-less `npx react-router` usage ([#12925](https://github.com/remix-run/react-router/pull/12925))\n- `@react-router/dev` - Skip action-only resource routes when using `prerender:true` ([#13004](https://github.com/remix-run/react-router/pull/13004))\n- `@react-router/dev` - Enhance invalid export detection when using `ssr:false` ([#12948](https://github.com/remix-run/react-router/pull/12948))\n - `headers`/`action` functions are prohibited in all routes with `ssr:false` because there will be no runtime server on which to run them\n - `loader` functions are more nuanced and depend on whether a given route is prerendered\n - When using `ssr:false` without a `prerender` config, only the `root` route can have a `loader`\n - When using `ssr:false` with a `prerender` config, only routes matched by a `prerender` path can have a `loader`\n- `@react-router/dev` - Error at build time in `ssr:false` + `prerender` apps for the edge case scenario of: ([#13021](https://github.com/remix-run/react-router/pull/13021))\n - A parent route has only a `loader` (does not have a `clientLoader`)\n - The parent route is pre-rendered\n - The parent route has children routes which are not prerendered\n - This means that when the child paths are loaded via the SPA fallback, the parent won't have any `loaderData` because there is no server on which to run the `loader`\n - This can be resolved by either adding a parent `clientLoader` or pre-rendering the child paths\n - If you add a `clientLoader`, calling the `serverLoader()` on non-prerendered paths will throw a 404\n- `@react-router/dev` - Limit prerendered resource route `.data` files to only the target route ([#13004](https://github.com/remix-run/react-router/pull/13004))\n- `@react-router/dev` - Fix pre-rendering of binary files ([#13039](https://github.com/remix-run/react-router/pull/13039))\n- `@react-router/dev` - Fix typegen for repeated params ([#13012](https://github.com/remix-run/react-router/pull/13012))\n - In React Router, path parameters are keyed by their name, so for a path pattern like `/a/:id/b/:id?/c/:id`, the last `:id` will set the value for `id` in `useParams` and the `params` prop\n - For example, `/a/1/b/2/c/3` will result in the value `{ id: 3 }` at runtime\n - Previously, generated types for params incorrectly modeled repeated params with an array\n - For example, `/a/1/b/2/c/3` generated a type like `{ id: [1,2,3] }`.\n - To be consistent with runtime behavior, the generated types now correctly model the \"last one wins\" semantics of path parameters.\n - For example, `/a/1/b/2/c/3` now generates a type like `{ id: 3 }`.\n- `@react-router/dev` - Fix path to load `package.json` for `react-router --version` ([#13012](https://github.com/remix-run/react-router/pull/13012))\n\n### Unstable Changes\n\nโš ๏ธ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_\n\n- `react-router` - Add `unstable_SerializesTo` brand type for library authors to register types serializable by React Router's streaming format (`turbo-stream`) ([#12264](https://github.com/remix-run/react-router/pull/12264))\n- `@react-router/dev` - Add unstable support for splitting route modules in framework mode via `future.unstable_splitRouteModules` ([#11871](https://github.com/remix-run/react-router/pull/11871))\n- `@react-router/dev` - Add `future.unstable_viteEnvironmentApi` flag to enable experimental Vite Environment API support ([#12936](https://github.com/remix-run/react-router/pull/12936))\n\n#### Split Route Modules (unstable)\n\n> โš ๏ธ This feature is currently [unstable](https://reactrouter.com/community/api-development-strategy#unstable-flags), enabled by the `future.unstable_splitRouteModules` flag. Weโ€™d love any interested users to play with it locally and provide feedback, but we do not recommend using it in production yet.\n>\n> If you do choose to adopt this flag in production, please ensure you do sufficient testing against your production build to ensure that the optimization is working as expected.\n\nOne of the conveniences of the [Route Module API](https://reactrouter.com/start/framework/route-module) is that everything a route needs is in a single file. Unfortunately this comes with a performance cost in some cases when using the `clientLoader`, `clientAction`, and `HydrateFallback` APIs.\n\nAs a basic example, consider this route module:\n\n```tsx filename=routes/example.tsx\nimport { MassiveComponent } from \"~/components\";\n\nexport async function clientLoader() {\n return await fetch(\"https://example.com/api\").then((response) =>\n response.json(),\n );\n}\n\nexport default function Component({ loaderData }) {\n return ;\n}\n```\n\nIn this example we have a minimal `clientLoader` export that makes a basic fetch call, whereas the default component export is much larger. This is a problem for performance because it means that if we want to navigate to this route client-side, the entire route module must be downloaded before the client loader can start running.\n\nTo visualize this as a timeline:\n\nIn the following timeline diagrams, different characters are used within the Route Module bars to denote the different Route Module APIs being exported.\n\n```\nGet Route Module: |--=======|\nRun clientLoader: |-----|\nRender: |-|\n```\n\nInstead, we want to optimize this to the following:\n\n```\nGet clientLoader: |--|\nGet Component: |=======|\nRun clientLoader: |-----|\nRender: |-|\n```\n\nTo achieve this optimization, React Router will split the route module into multiple smaller modules during the production build process. In this case, we'll end up with two separate [virtual modules](https://vite.dev/guide/api-plugin#virtual-modules-convention) โ€” one for the client loader and one for the component and its dependencies.\n\n```tsx filename=routes/example.tsx?route-chunk=clientLoader\nexport async function clientLoader() {\n return await fetch(\"https://example.com/api\").then((response) =>\n response.json(),\n );\n}\n```\n\n```tsx filename=routes/example.tsx?route-chunk=main\nimport { MassiveComponent } from \"~/components\";\n\nexport default function Component({ loaderData }) {\n return ;\n}\n```\n\n> ๐Ÿ’ก This optimization is automatically applied in framework mode, but you can also implement it in library mode via `route.lazy` and authoring your route in multiple files as covered in our blog post on [lazy loading route modules.](https://remix.run/blog/lazy-loading-routes#advanced-usage-and-optimizations)\n\nNow that these are available as separate modules, the client loader and the component can be downloaded in parallel. This means that the client loader can be executed as soon as it's ready without having to wait for the component.\n\nThis optimization is even more pronounced when more Route Module APIs are used. For example, when using `clientLoader`, `clientAction` and `HydrateFallback`, the timeline for a single route module during a client-side navigation might look like this:\n\n```\nGet Route Module: |--~~++++=======|\nRun clientLoader: |-----|\nRender: |-|\n```\n\nThis would instead be optimized to the following:\n\n```\nGet clientLoader: |--|\nGet clientAction: |~~|\nGet HydrateFallback: SKIPPED\nGet Component: |=======|\nRun clientLoader: |-----|\nRender: |-|\n```\n\nNote that this optimization only works when the Route Module APIs being split don't share code within the same file. For example, the following route module can't be split:\n\n```tsx filename=routes/example.tsx\nimport { MassiveComponent } from \"~/components\";\n\nconst shared = () => console.log(\"hello\");\n\nexport async function clientLoader() {\n shared();\n return await fetch(\"https://example.com/api\").then((response) =>\n response.json(),\n );\n}\n\nexport default function Component({ loaderData }) {\n shared();\n return ;\n}\n```\n\nThis route will still work, but since both the client loader and the component depend on the `shared` function defined within the same file, it will be de-optimized into a single route module.\n\nTo avoid this, you can extract any code shared between exports into a separate file. For example:\n\n```tsx filename=routes/example/shared.tsx\nexport const shared = () => console.log(\"hello\");\n```\n\nYou can then import this shared code in your route module without triggering the de-optimization:\n\n```tsx filename=routes/example/route.tsx\nimport { MassiveComponent } from \"~/components\";\nimport { shared } from \"./shared\";\n\nexport async function clientLoader() {\n shared();\n return await fetch(\"https://example.com/api\").then((response) =>\n response.json(),\n );\n}\n\nexport default function Component({ loaderData }) {\n shared();\n return ;\n}\n```\n\nSince the shared code is in its own module, React Router is now able to split this route module into two separate virtual modules:\n\n```tsx filename=routes/example/route.tsx?route-chunk=clientLoader\nimport { shared } from \"./shared\";\n\nexport async function clientLoader() {\n shared();\n return await fetch(\"https://example.com/api\").then((response) =>\n response.json(),\n );\n}\n```\n\n```tsx filename=routes/example/route.tsx?route-chunk=main\nimport { MassiveComponent } from \"~/components\";\nimport { shared } from \"./shared\";\n\nexport default function Component({ loaderData }) {\n shared();\n return ;\n}\n```\n\nIf your project is particularly performance sensitive, you can set the `unstable_splitRouteModules` future flag to `\"enforce\"`:\n\n```tsx filename=react-router-config.ts\nexport default {\n future: {\n unstable_splitRouteModules: \"enforce\",\n },\n};\n```\n\nThis setting will raise an error if any route modules can't be split:\n\n```\nError splitting route module: routes/example/route.tsx\n\n- clientLoader\n\nThis export could not be split into its own chunk because it shares code with other exports. You should extract any shared code into its own module and then import it within the route module.\n```\n\n### Changes by Package\n\n- [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/create-react-router/CHANGELOG.md#720)\n- [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router/CHANGELOG.md#720)\n- [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-architect/CHANGELOG.md#720)\n- [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-cloudflare/CHANGELOG.md#720)\n- [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-dev/CHANGELOG.md#720)\n- [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-express/CHANGELOG.md#720)\n- [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-fs-routes/CHANGELOG.md#720)\n- [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-node/CHANGELOG.md#720)\n- [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#720)\n- [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-serve/CHANGELOG.md#720)\n\n**Full Changelog**: [`v7.1.5...v7.2.0`](https://github.com/remix-run/react-router/compare/react-router@7.1.5...react-router@7.2.0)\n\n## v7.1.5\n\nDate: 2025-01-31\n\n### Patch Changes\n\n- `react-router` - Fix regression introduced in `7.1.4` via [#12800](https://github.com/remix-run/react-router/pull/12800) that caused issues navigating to hash routes inside splat routes for applications using Lazy Route Discovery (`patchRoutesOnNavigation`) ([#12927](https://github.com/remix-run/react-router/pull/12927))\n\n**Full Changelog**: [`v7.1.4...v7.1.5`](https://github.com/remix-run/react-router/compare/react-router@7.1.4...react-router@7.1.5)\n\n## v7.1.4\n\nDate: 2025-01-30\n\n### Patch Changes\n\n- `@react-router/dev` - Properly resolve Windows file paths to scan for Vite's dependency optimization when using the `unstable_optimizeDeps` future flag ([#12637](https://github.com/remix-run/react-router/pull/12637))\n- `@react-router/dev` - Fix prerendering when using a custom server - previously we ended up trying to import the users custom server when we actually want to import the virtual server build module ([#12759](https://github.com/remix-run/react-router/pull/12759))\n- `react-router` - Properly handle status codes that cannot have a body in single fetch responses (204, etc.) ([#12760](https://github.com/remix-run/react-router/pull/12760))\n- `react-router` - Properly bubble headers as `errorHeaders` when throwing a `data()` result ([#12846](https://github.com/remix-run/react-router/pull/12846))\n - Avoid duplication of `Set-Cookie` headers if also returned from `headers`\n- `react-router` - Stop erroring on resource routes that return raw strings/objects and instead serialize them as `text/plain` or `application/json` responses ([#12848](https://github.com/remix-run/react-router/pull/12848))\n - This only applies when accessed as a resource route without the `.data` extension\n - When accessed from a Single Fetch `.data` request, they will still be encoded via `turbo-stream`\n- `react-router` - Optimize Lazy Route Discovery path discovery to favor a single `querySelectorAll` call at the `body` level instead of many calls at the sub-tree level ([#12731](https://github.com/remix-run/react-router/pull/12731))\n- `react-router` - Optimize route matching by skipping redundant `matchRoutes` calls when possible ([#12800](https://github.com/remix-run/react-router/pull/12800), [#12882](https://github.com/remix-run/react-router/pull/12882))\n- `react-router` - Internal reorg to clean up some duplicated route module types ([#12799](https://github.com/remix-run/react-router/pull/12799))\n\n**Full Changelog**: [`v7.1.3...v7.1.4`](https://github.com/remix-run/react-router/compare/react-router@7.1.3...react-router@7.1.4)\n\n## v7.1.3\n\nDate: 2025-01-17\n\n### Patch Changes\n\n- `@react-router/dev` - Fix `reveal` and `routes` CLI commands ([#12745](https://github.com/remix-run/react-router/pull/12745))\n\n**Full Changelog**: [`v7.1.2...v7.1.3`](https://github.com/remix-run/react-router/compare/react-router@7.1.2...react-router@7.1.3)\n\n## v7.1.2\n\nDate: 2025-01-16\n\n### Patch Changes\n\n- `react-router` - Fix issue with fetcher data cleanup in the data layer on fetcher unmount ([#12681](https://github.com/remix-run/react-router/pull/12681))\n- `react-router` - Do not rely on `symbol` for filtering out `redirect` responses from loader data ([#12694](https://github.com/remix-run/react-router/pull/12694))\n - Previously, some projects were getting type checking errors like:\n ```ts\n error TS4058: Return type of exported function has or is using name 'redirectSymbol' from external module \"node_modules/...\" but cannot be named.\n ```\n - Now that `symbol`s are not used for the `redirect` response type, these errors should no longer be present\n- `@react-router/dev` - Fix default external conditions in Vite v6 ([#12644](https://github.com/remix-run/react-router/pull/12644))\n - This fixes resolution issues with certain npm packages\n- `@react-router/dev` - Fix mismatch in prerendering html/data files when path is missing a leading slash ([#12684](https://github.com/remix-run/react-router/pull/12684))\n- `@react-router/dev` - Use `module-sync` server condition when enabled in the runtime. This fixes React context mismatches (e.g. `useHref() may be used only in the context of a component.`) during development on Node 22.10.0+ when using libraries that have a peer dependency on React Router ([#12729](https://github.com/remix-run/react-router/pull/12729))\n- `@react-router/dev` - Fix `react-refresh` source maps ([#12686](https://github.com/remix-run/react-router/pull/12686))\n\n**Full Changelog**: [`v7.1.1...v7.1.2`](https://github.com/remix-run/react-router/compare/react-router@7.1.1...react-router@7.1.2)\n\n## v7.1.1\n\nDate: 2024-12-23\n\n### Patch Changes\n\n- `@react-router/dev` - Fix for a crash when optional args are passed to the CLI ([#12609](https://github.com/remix-run/react-router/pull/12609))\n\n**Full Changelog**: [`v7.1.0...v7.1.1`](https://github.com/remix-run/react-router/compare/react-router@7.1.0...react-router@7.1.1)\n\n## v7.1.0\n\nDate: 2024-12-20\n\n### Minor Changes\n\n- Add support for Vite v6 ([#12469](https://github.com/remix-run/react-router/pull/12469))\n\n### Patch Changes\n\n- `react-router` - Throw unwrapped Single Fetch `redirect` to align with pre-Single Fetch behavior ([#12506](https://github.com/remix-run/react-router/pull/12506))\n- `react-router` - Ignore redirects when inferring loader data types ([#12527](https://github.com/remix-run/react-router/pull/12527))\n- `react-router` - Remove `` warning which suffers from false positives in a lazy route discovery world ([#12485](https://github.com/remix-run/react-router/pull/12485))\n- `create-react-router` - Fix missing `fs-extra` dependency ([#12556](https://github.com/remix-run/react-router/pull/12556))\n- `@react-router/dev`/`@react-router/serve` - Properly initialize `NODE_ENV` if not already set for compatibility with React 19 ([#12578](https://github.com/remix-run/react-router/pull/12578))\n- `@react-router/dev` - Remove the leftover/unused `abortDelay` prop from `ServerRouter` and update the default `entry.server.tsx` to use the new `streamTimeout` value for Single Fetch ([#12478](https://github.com/remix-run/react-router/pull/12478))\n - The `abortDelay` functionality was removed in v7 as it was coupled to the `defer` implementation from Remix v2, but this removal of this prop was missed\n - If you were still using this prop in your `entry.server` file, it's likely your app is not aborting streams as you would expect and you will need to adopt the new [`streamTimeout`](https://reactrouter.com/explanation/special-files#streamtimeout) value introduced with Single Fetch\n- `@react-router/fs-routes` - Throw error in `flatRoutes` if routes directory is missing ([#12407](https://github.com/remix-run/react-router/pull/12407))\n\n### Changes by Package\n\n- [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/create-react-router/CHANGELOG.md#710)\n- [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router/CHANGELOG.md#710)\n- [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-architect/CHANGELOG.md#710)\n- [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-cloudflare/CHANGELOG.md#710)\n- [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-dev/CHANGELOG.md#710)\n- [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-express/CHANGELOG.md#710)\n- [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-fs-routes/CHANGELOG.md#710)\n- [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-node/CHANGELOG.md#710)\n- [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#710)\n- [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-serve/CHANGELOG.md#710)\n\n**Full Changelog**: [`v7.0.2...v7.1.0`](https://github.com/remix-run/react-router/compare/react-router@7.0.2...react-router@7.1.0)\n\n## v7.0.2\n\nDate: 2024-12-02\n\n### Patch Changes\n\n- `react-router` - Temporarily only use one build in export map so packages can have a peer dependency on react router ([#12437](https://github.com/remix-run/react-router/pull/12437))\n- `@react-router/dev` - Support `moduleResolution` `Node16` and `NodeNext` ([#12440](https://github.com/remix-run/react-router/pull/12440))\n- `@react-router/dev` - Generate wide `matches` and `params` types for child routes ([#12397](https://github.com/remix-run/react-router/pull/12397))\n - At runtime, `matches` includes child route matches and `params` include child route path parameters\n - But previously, we only generated types for parent routes and the current route in `matches` and `params`\n - To align our generated types more closely to the runtime behavior, we now generate more permissive, wider types when accessing child route information\n\n**Full Changelog**: [`v7.0.1...v7.0.2`](https://github.com/remix-run/react-router/compare/react-router@7.0.1...react-router@7.0.2)\n\n## v7.0.1\n\nDate: 2024-11-22\n\n### Patch Changes\n\n- `@react-router/dev` - Ensure typegen file watcher is cleaned up when Vite dev server restarts ([#12331](https://github.com/remix-run/react-router/pull/12331))\n- `@react-router/dev` - Pass route `error` to `ErrorBoundary` as a prop ([#12338](https://github.com/remix-run/react-router/pull/12338))\n\n**Full Changelog**: [`v7.0.0...v7.0.1`](https://github.com/remix-run/react-router/compare/react-router@7.0.0...react-router@7.0.1)\n\n## v7.0.0\n\nDate: 2024-11-21\n\n### Breaking Changes\n\n#### Package Restructuring\n\n- The `react-router-dom`, `@remix-run/react`, `@remix-run/server-runtime`, and `@remix-run/router` have been collapsed into the `react-router` package\n - To ease migration, `react-router-dom` is still published in v7 as a re-export of everything from `react-router`\n- The `@remix-run/cloudflare-pages` and `@remix-run/cloudflare-workers` have been collapsed into `@react-router/cloudflare` package`\n- The `react-router-dom-v5-compat` and `react-router-native` packages are removed starting with v7\n\n#### Removed Adapter Re-exports\n\nRemix v2 used to re-export all common `@remix-run/server-runtime` APIs through the various runtime packages (`node`, `cloudflare`, `deno`) so that you wouldn't need an additional `@remix-run/server-runtime` dependency in your `package.json`. With the collapsing of packages into `react-router`, these common APIs are now no longer re-exported through the runtime adapters. You should import all common APIs from `react-router`, and only import runtime-specific APIs from the runtime packages:\n\n```jsx\n// Runtime-specific APIs\nimport { createFileSessionStorage } from \"@react-router/node\";\n// Runtime-agnostic APIs\nimport { redirect, useLoaderData } from \"react-router\";\n```\n\n#### Removed APIs\n\nThe following APIs have been removed in React Router v7:\n\n- `json`\n- `defer`\n- `unstable_composeUploadHandlers`\n- `unstable_createMemoryUploadHandler`\n- `unstable_parseMultipartFormData`\n\n#### Minimum Versions\n\nReact Router v7 requires the following minimum versions:\n\n- `node@20`\n - React Router no longer provides an `installGlobals` method to [polyfill](https://reactrouter.com/dev/guides/deploying/custom-node#polyfilling-fetch) the `fetch` API\n- `react@18`, `react-dom@18`\n\n#### Adopted Future Flag Behaviors\n\nRemix and React Router follow an [API Development Strategy](https://reactrouter.com/en/main/guides/api-development-strategy) leveraging \"Future Flags\" to avoid introducing a slew of breaking changes in a major release. Instead, breaking changes are introduced in minor releases behind a flag, allowing users to opt-in at their convenience. In the next major release, all future flag behaviors become the default behavior.\n\nThe following previously flagged behaviors are now the default in React Router v7:\n\n- [React Router v6 flags](https://reactrouter.com/en/v6/upgrading/future)\n - `future.v7_relativeSplatPath`\n - `future.v7_startTransition`\n - `future.v7_fetcherPersist`\n - `future.v7_normalizeFormMethod`\n - `future.v7_partialHydration`\n - `future.v7_skipActionStatusRevalidation`\n- [Remix v2 flags](https://remix.run/docs/en/v2/start/future-flags)\n - `future.v3_fetcherPersist`\n - `future.v3_relativeSplatPath`\n - `future.v3_throwAbortReason`\n - `future.v3_singleFetch`\n - `future.v3_lazyRouteDiscovery`\n - `future.v3_optimizeDeps`\n\n#### Vite Compiler\n\nThe [Remix Vite plugin](https://remix.run/docs/en/2.12.1/start/future-flags#vite-plugin) is the proper way to build full-stack SSR apps using React Router v7. The former `esbuild`-based compiler is no longer available.\n\n**Renamed `vitePlugin` and `cloudflareDevProxyVitePlugin`**\n\nFor Remix consumers migrating to React Router, the `vitePlugin` and `cloudflareDevProxyVitePlugin` exports have been renamed and moved ([#11904](https://github.com/remix-run/react-router/pull/11904))\n\n```diff\n-import {\n- vitePlugin as remix,\n- cloudflareDevProxyVitePlugin,\n-} from \"@remix/dev\";\n\n+import { reactRouter } from \"@react-router/dev/vite\";\n+import { cloudflareDevProxy } from \"@react-router/dev/vite/cloudflare\";\n```\n\n**Removed `manifest` option**\n\nFor Remix consumers migrating to React Router, the Vite plugin's `manifest` option has been removed. The `manifest` option been superseded by the more powerful `buildEnd` hook since it's passed the `buildManifest` argument. You can still write the build manifest to disk if needed, but you'll most likely find it more convenient to write any logic depending on the build manifest within the `buildEnd` hook itself. ([#11573](https://github.com/remix-run/react-router/pull/11573))\n\nIf you were using the `manifest` option, you can replace it with a `buildEnd` hook that writes the manifest to disk like this:\n\n```js\n// react-router.config.ts\nimport { type Config } from \"@react-router/dev/config\";\nimport { writeFile } from \"node:fs/promises\";\n\nexport default {\n async buildEnd({ buildManifest }) {\n await writeFile(\n \"build/manifest.json\",\n JSON.stringify(buildManifest, null, 2),\n \"utf-8\"\n );\n },\n} satisfies Config;\n```\n\n#### Exposed Router Promises\n\nBecause React 19 will have first-class support for handling promises in the render pass (via `React.use` and `useAction`), we are now comfortable exposing the promises for the APIs that previously returned `undefined`:\n\n- `useNavigate()`\n- `useSubmit()`\n- `useFetcher().load`\n- `useFetcher().submit`\n- `useRevalidator().revalidate()`\n\n### Other Notable Changes\n\n#### `routes.ts`\n\nWhen using the React Router Vite plugin, routes are defined in `app/routes.ts`. Route config is exported via the `routes` export, conforming to the `RouteConfig` type. Route helper functions `route`, `index`, and `layout` are provided to make declarative type-safe route definitions easier.\n\n```ts\n// app/routes.ts\nimport {\n type RouteConfig,\n route,\n index,\n layout,\n} from \"@react-router/dev/routes\";\n\nexport const routes: RouteConfig = [\n index(\"./home.tsx\"),\n route(\"about\", \"./about.tsx\"),\n\n layout(\"./auth/layout.tsx\", [\n route(\"login\", \"./auth/login.tsx\"),\n route(\"register\", \"./auth/register.tsx\"),\n ]),\n\n route(\"concerts\", [\n index(\"./concerts/home.tsx\"),\n route(\":city\", \"./concerts/city.tsx\"),\n route(\"trending\", \"./concerts/trending.tsx\"),\n ]),\n];\n```\n\nFor Remix consumers migrating to React Router, you can still configure file system routing within `routes.ts` using the `@react-router/fs-routes` package. A minimal route config that reproduces the default Remix setup looks like this:\n\n```ts\n// app/routes.ts\nimport { type RouteConfig } from \"@react-router/dev/routes\";\nimport { flatRoutes } from \"@react-router/fs-routes\";\n\nexport const routes: RouteConfig = flatRoutes();\n```\n\nIf you want to migrate from file system routing to config-based routes, you can mix and match approaches by spreading the results of the async `flatRoutes` function into the array of config-based routes.\n\n```ts\n// app/routes.ts\nimport { type RouteConfig, route } from \"@react-router/dev/routes\";\nimport { flatRoutes } from \"@react-router/fs-routes\";\n\nexport const routes: RouteConfig = [\n // Example config-based route:\n route(\"/hello\", \"./routes/hello.tsx\"),\n\n // File system routes scoped to a different directory:\n ...(await flatRoutes({\n rootDirectory: \"fs-routes\",\n })),\n];\n```\n\nIf you were using Remix's `routes` option to use alternative file system routing conventions, you can adapt these to the new `RouteConfig` format using `@react-router/remix-config-routes-adapter`.\n\nFor example, if you were using [Remix v1 route conventions](https://remix.run/docs/en/1.19.3/file-conventions/routes-files) in Remix v2, you can combine `@react-router/remix-config-routes-adapter` with `@remix-run/v1-route-convention` to adapt this to React Router:\n\n```ts\n// app/routes.ts\nimport { type RouteConfig } from \"@react-router/dev/routes\";\nimport { remixConfigRoutes } from \"@react-router/remix-config-routes-adapter\";\nimport { createRoutesFromFolders } from \"@remix-run/v1-route-convention\";\n\nexport const routes: RouteConfig = remixConfigRoutes(async (defineRoutes) => {\n return createRoutesFromFolders(defineRoutes, {\n ignoredFilePatterns: [\"**/.*\", \"**/*.css\"],\n });\n});\n```\n\nAlso note that, if you were using Remix's `routes` option to define config-based routes, you can also adapt these to the new `RouteConfig` format using `@react-router/remix-config-routes-adapter` with minimal code changes. While this makes for a fast migration path, we recommend migrating any config-based routes from Remix to the new `RouteConfig` format since it's a fairly straightforward migration.\n\n```diff\n// app/routes.ts\n-import { type RouteConfig } from \"@react-router/dev/routes\";\n+import { type RouteConfig, route } from \"@react-router/dev/routes\";\n-import { remixConfigRoutes } from \"@react-router/remix-config-routes-adapter\";\n\n-export const routes: RouteConfig = remixConfigRoutes(async (defineRoutes) => {\n- defineRoutes((route) => {\n- route(\"/parent\", \"./routes/parent.tsx\", () => [\n- route(\"/child\", \"./routes/child.tsx\"),\n- ]);\n- });\n-});\n+export const routes: RouteConfig = [\n+ route(\"/parent\", \"./routes/parent.tsx\", [\n+ route(\"/child\", \"./routes/child.tsx\"),\n+ ]),\n+];\n```\n\n#### Type-safety improvements\n\nReact Router now generates types for each of your route modules and passes typed props to route module component exports ([#11961](https://github.com/remix-run/react-router/pull/11961), [#12019](https://github.com/remix-run/react-router/pull/12019)). You can access those types by importing them from `./+types/`.\n\nSee [_How To > Route Module Type Safety_](https://reactrouter.com/dev/how-to/route-module-type-safety) and [_Explanations > Type Safety_](https://reactrouter.com/dev/explanation/type-safety) for more details.\n\n#### Prerendering\n\nReact Router v7 includes a new `prerender` config in the vite plugin to support SSG use-cases. This will pre-render your `.html` and `.data` files at build time and so you can serve them statically at runtime from a running server or a CDN ([#11539](https://github.com/remix-run/react-router/pull/11539))\n\n```ts\nexport default defineConfig({\n plugins: [\n reactRouter({\n async prerender({ getStaticPaths }) {\n let slugs = await fakeGetSlugsFromCms();\n return [\n ...getStaticPaths(),\n ...slugs.map((slug) => `/product/${slug}`),\n ];\n },\n }),\n tsconfigPaths(),\n ],\n});\n\nasync function fakeGetSlugsFromCms() {\n await new Promise((r) => setTimeout(r, 1000));\n return [\"shirt\", \"hat\"];\n}\n```\n\n### Major Changes (`react-router`)\n\n- Remove the original `defer` implementation in favor of using raw promises via single fetch and `turbo-stream` ([#11744](https://github.com/remix-run/react-router/pull/11744))\n - This removes these exports from React Router:\n - `defer`\n - `AbortedDeferredError`\n - `type TypedDeferredData`\n - `UNSAFE_DeferredData`\n - `UNSAFE_DEFERRED_SYMBOL`\n- Collapse packages into `react-router`([#11505](https://github.com/remix-run/react-router/pull/11505))\n - `@remix-run/router`\n - `react-router-dom`\n - `@remix-run/server-runtime`\n - `@remix-run/testing`\n - As a note, the `react-router-dom` package is maintained to ease adoption but it simply re-exports all APIs from `react-router`\n- Drop support for Node 16, React Router SSR now requires Node 18 or higher ([#11391](https://github.com/remix-run/react-router/pull/11391), [#11690](https://github.com/remix-run/react-router/pull/11690))\n- Remove `future.v7_startTransition` flag ([#11696](https://github.com/remix-run/react-router/pull/11696))\n- Expose the underlying router promises from the following APIs for composition in React 19 APIs: ([#11521](https://github.com/remix-run/react-router/pull/11521))\n- Remove `future.v7_normalizeFormMethod` future flag ([#11697](https://github.com/remix-run/react-router/pull/11697))\n- Imports/Exports cleanup ([#11840](https://github.com/remix-run/react-router/pull/11840))\n - Removed the following exports that were previously public API from `@remix-run/router`\n - types\n - `AgnosticDataIndexRouteObject`\n - `AgnosticDataNonIndexRouteObject`\n - `AgnosticDataRouteMatch`\n - `AgnosticDataRouteObject`\n - `AgnosticIndexRouteObject`\n - `AgnosticNonIndexRouteObject`\n - `AgnosticRouteMatch`\n - `AgnosticRouteObject`\n - `TrackedPromise`\n - `unstable_AgnosticPatchRoutesOnMissFunction`\n - `Action` -> exported as `NavigationType` via `react-router`\n - `Router` exported as `RemixRouter` to differentiate from RR's ``\n - API\n - `getToPathname` (`@private`)\n - `joinPaths` (`@private`)\n - `normalizePathname` (`@private`)\n - `resolveTo` (`@private`)\n - `stripBasename` (`@private`)\n - `createBrowserHistory` -> in favor of `createBrowserRouter`\n - `createHashHistory` -> in favor of `createHashRouter`\n - `createMemoryHistory` -> in favor of `createMemoryRouter`\n - `createRouter`\n - `createStaticHandler` -> in favor of wrapper `createStaticHandler` in RR Dom\n - `getStaticContextFromError`\n - Removed the following exports that were previously public API from `react-router`\n - `Hash`\n - `Pathname`\n - `Search`\n- Remove `future.v7_prependBasename` from the internalized `@remix-run/router` package ([#11726](https://github.com/remix-run/react-router/pull/11726))\n- Remove `future.v7_throwAbortReason` from internalized `@remix-run/router` package ([#11728](https://github.com/remix-run/react-router/pull/11728))\n- Add `exports` field to all packages ([#11675](https://github.com/remix-run/react-router/pull/11675))\n- Renamed `RemixContext` to `FrameworkContext` ([#11705](https://github.com/remix-run/react-router/pull/11705))\n- Update the minimum React version to 18 ([#11689](https://github.com/remix-run/react-router/pull/11689))\n- `PrefetchPageDescriptor` replaced by `PageLinkDescriptor` ([#11960](https://github.com/remix-run/react-router/pull/11960))\n- Remove the `future.v7_partialHydration` flag ([#11725](https://github.com/remix-run/react-router/pull/11725))\n - This also removes the `` prop\n - To migrate, move the `fallbackElement` to a `hydrateFallbackElement`/`HydrateFallback` on your root route\n - Also worth nothing there is a related breaking changer with this future flag:\n - Without `future.v7_partialHydration` (when using `fallbackElement`), `state.navigation` was populated during the initial load\n - With `future.v7_partialHydration`, `state.navigation` remains in an `\"idle\"` state during the initial load\n- Remove `future.v7_relativeSplatPath` future flag ([#11695](https://github.com/remix-run/react-router/pull/11695))\n- Remove remaining future flags ([#11820](https://github.com/remix-run/react-router/pull/11820))\n - React Router `v7_skipActionErrorRevalidation`\n - Remix `v3_fetcherPersist`, `v3_relativeSplatPath`, `v3_throwAbortReason`\n- Rename `createRemixStub` to `createRoutesStub` ([#11692](https://github.com/remix-run/react-router/pull/11692))\n- Remove `@remix-run/router` deprecated `detectErrorBoundary` option in favor of `mapRouteProperties` ([#11751](https://github.com/remix-run/react-router/pull/11751))\n- Add `react-router/dom` subpath export to properly enable `react-dom` as an optional `peerDependency` ([#11851](https://github.com/remix-run/react-router/pull/11851))\n - This ensures that we don't blindly `import ReactDOM from \"react-dom\"` in `` in order to access `ReactDOM.flushSync()`, since that would break `createMemoryRouter` use cases in non-DOM environments\n - DOM environments should import from `react-router/dom` to get the proper component that makes `ReactDOM.flushSync()` available:\n - If you are using the Vite plugin, use this in your `entry.client.tsx`:\n - `import { HydratedRouter } from 'react-router/dom'`\n - If you are not using the Vite plugin and are manually calling `createBrowserRouter`/`createHashRouter`:\n - `import { RouterProvider } from \"react-router/dom\"`\n- Remove `future.v7_fetcherPersist` flag ([#11731](https://github.com/remix-run/react-router/pull/11731))\n- Allow returning `undefined` from loaders and actions ([#11680](https://github.com/remix-run/react-router/pull/11680), [#12057]([https://github.com/remix-run/react-router/pull/1205))\n- Use `createRemixRouter`/`RouterProvider` in `entry.client` instead of `RemixBrowser` ([#11469](https://github.com/remix-run/react-router/pull/11469))\n- Remove the deprecated `json` utility ([#12146](https://github.com/remix-run/react-router/pull/12146))\n - You can use [`Response.json`](https://developer.mozilla.org/en-US/docs/Web/API/Response/json_static) if you still need to construct JSON responses in your app\n\n### Major Changes (`@react-router/*`)\n\n- Remove `future.v3_singleFetch` flag ([#11522](https://github.com/remix-run/react-router/pull/11522))\n- Drop support for Node 16 and 18, update minimum Node version to 20 ([#11690](https://github.com/remix-run/react-router/pull/11690), [#12171](https://github.com/remix-run/react-router/pull/12171))\n - Remove `installGlobals()` as this should no longer be necessary\n- Add `exports` field to all packages ([#11675](https://github.com/remix-run/react-router/pull/11675))\n- No longer re-export APIs from `react-router` through different runtime/adapter packages ([#11702](https://github.com/remix-run/react-router/pull/11702))\n- For Remix consumers migrating to React Router, the `crypto` global from the [Web Crypto API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_API) is now required when using cookie and session APIs\n - This means that the following APIs are provided from `react-router` rather than platform-specific packages: ([#11837](https://github.com/remix-run/react-router/pull/11837))\n - `createCookie`\n - `createCookieSessionStorage`\n - `createMemorySessionStorage`\n - `createSessionStorage`\n - For consumers running older versions of Node, the `installGlobals` function from `@remix-run/node` has been updated to define `globalThis.crypto`, using [Node's `require('node:crypto').webcrypto` implementation](https://nodejs.org/api/webcrypto.html)\n - Since platform-specific packages no longer need to implement this API, the following low-level APIs have been removed:\n - `createCookieFactory`\n - `createSessionStorageFactory`\n - `createCookieSessionStorageFactory`\n - `createMemorySessionStorageFactory`\n- Consolidate types previously duplicated across `@remix-run/router`, `@remix-run/server-runtime`, and `@remix-run/react` now that they all live in `react-router` ([#12177](https://github.com/remix-run/react-router/pull/12177))\n - Examples: `LoaderFunction`, `LoaderFunctionArgs`, `ActionFunction`, `ActionFunctionArgs`, `DataFunctionArgs`, `RouteManifest`, `LinksFunction`, `Route`, `EntryRoute`\n - The `RouteManifest` type used by the \"remix\" code is now slightly stricter because it is using the former `@remix-run/router` `RouteManifest`\n - `Record -> Record`\n - Removed `AppData` type in favor of inlining `unknown` in the few locations it was used\n - Removed `ServerRuntimeMeta*` types in favor of the `Meta*` types they were duplicated from\n- Migrate Remix v2 type generics to React Router ([#12180](https://github.com/remix-run/react-router/pull/12180))\n - These generics are provided for Remix v2 migration purposes\n - These generics and the APIs they exist on should be considered informally deprecated in favor of the new `Route.*` types\n - Anyone migrating from React Router v6 should probably not leverage these new generics and should migrate straight to the `Route.*` types\n - For React Router v6 users, these generics are new and should not impact your app, with one exception\n - `useFetcher` previously had an optional generic (used primarily by Remix v2) that expected the data type\n - This has been updated in v7 to expect the type of the function that generates the data (i.e., `typeof loader`/`typeof action`)\n - Therefore, you should update your usages:\n - โŒ `useFetcher()`\n - โœ… `useFetcher()`\n- Update `cookie` dependency to `^1.0.1` - please see the [release notes](https://github.com/jshttp/cookie/releases) for any breaking changes ([#12172](https://github.com/remix-run/react-router/pull/12172))\n- `@react-router/cloudflare` - For Remix consumers migrating to React Router, all exports from `@remix-run/cloudflare-pages` are now provided for React Router consumers in the `@react-router/cloudflare` package. There is no longer a separate package for Cloudflare Pages. ([#11801](https://github.com/remix-run/react-router/pull/11801))\n- `@react-router/cloudflare` - The `@remix-run/cloudflare-workers` package has been deprecated. Remix consumers migrating to React Router should use the `@react-router/cloudflare` package directly. For guidance on how to use `@react-router/cloudflare` within a Cloudflare Workers context, refer to the Cloudflare Workers template. ([#11801](https://github.com/remix-run/react-router/pull/11801))\n- `@react-router/dev` - For Remix consumers migrating to React Router, the `vitePlugin` and `cloudflareDevProxyVitePlugin` exports have been renamed and moved. ([#11904](https://github.com/remix-run/react-router/pull/11904))\n- `@react-router/dev` - For Remix consumers migrating to React Router who used the Vite plugin's `buildEnd` hook, the resolved `reactRouterConfig` object no longer contains a `publicPath` property since this belongs to Vite, not React Router ([#11575](https://github.com/remix-run/react-router/pull/11575))\n- `@react-router/dev` - For Remix consumers migrating to React Router, the Vite plugin's `manifest` option has been removed ([#11573](https://github.com/remix-run/react-router/pull/11573))\n- `@react-router/dev` - Update default `isbot` version to v5 and drop support for `isbot@3` ([#11770](https://github.com/remix-run/react-router/pull/11770))\n - If you have `isbot@4` or `isbot@5` in your `package.json`:\n - You do not need to make any changes\n - If you have `isbot@3` in your `package.json` and you have your own `entry.server.tsx` file in your repo\n - You do not need to make any changes\n - You can upgrade to `isbot@5` independent of the React Router v7 upgrade\n - If you have `isbot@3` in your `package.json` and you do not have your own `entry.server.tsx` file in your repo\n - You are using the internal default entry provided by React Router v7 and you will need to upgrade to `isbot@5` in your `package.json`\n- `@react-router/dev` - For Remix consumers migrating to React Router, Vite manifests (i.e. `.vite/manifest.json`) are now written within each build subdirectory, e.g. `build/client/.vite/manifest.json` and `build/server/.vite/manifest.json` instead of `build/.vite/client-manifest.json` and `build/.vite/server-manifest.json`. This means that the build output is now much closer to what you'd expect from a typical Vite project. ([#11573](https://github.com/remix-run/react-router/pull/11573))\n - Originally the Remix Vite plugin moved all Vite manifests to a root-level `build/.vite` directory to avoid accidentally serving them in production, particularly from the client build. This was later improved with additional logic that deleted these Vite manifest files at the end of the build process unless Vite's `build.manifest` had been enabled within the app's Vite config. This greatly reduced the risk of accidentally serving the Vite manifests in production since they're only present when explicitly asked for. As a result, we can now assume that consumers will know that they need to manage these additional files themselves, and React Router can safely generate a more standard Vite build output.\n\n### Minor Changes\n\n- `react-router` - Params, loader data, and action data as props for route component exports ([#11961](https://github.com/remix-run/react-router/pull/11961))\n- `react-router` - Add route module type generation ([#12019](https://github.com/remix-run/react-router/pull/12019))\n- `react-router` - Remove duplicate `RouterProvider` implementations ([#11679](https://github.com/remix-run/react-router/pull/11679))\n- `react-router` - Stabilize `unstable_dataStrategy` ([#11969](https://github.com/remix-run/react-router/pull/11969))\n- `react-router` - Stabilize `unstable_patchRoutesOnNavigation` ([#11970](https://github.com/remix-run/react-router/pull/11970))\n- `react-router` - Add prefetching support to `Link`/`NavLink` when using Remix SSR ([#11402](https://github.com/remix-run/react-router/pull/11402))\n- `react-router` - Enhance `ScrollRestoration` so it can restore properly on an SSR'd document load ([#11401](https://github.com/remix-run/react-router/pull/11401))\n- `@react-router/dev` - Add support for the `prerender` config in the React Router vite plugin, to support existing SSG use-cases ([#11539](https://github.com/remix-run/react-router/pull/11539))\n- `@react-router/dev` - Remove internal `entry.server.spa.tsx` implementation which was not compatible with the Single Fetch async hydration approach ([#11681](https://github.com/remix-run/react-router/pull/11681))\n- `@react-router/serve`: Update `express.static` configurations to support new `prerender` API ([#11547](https://github.com/remix-run/react-router/pull/11547))\n - Assets in the `build/client/assets` folder are served as before, with a 1-year immutable `Cache-Control` header\n - Static files outside of assets, such as pre-rendered `.html` and `.data` files are not served with a specific `Cache-Control` header\n - `.data` files are served with `Content-Type: text/x-turbo`\n - For some reason, when adding this via `express.static`, it seems to also add a `Cache-Control: public, max-age=0` to `.data` files\n\n### Patch Changes\n\n- Replace `substr` with `substring` ([#12080](https://github.com/remix-run/react-router/pull/12080))\n- `react-router` - Fix redirects returned from loaders/actions using `data()` ([#12021](https://github.com/remix-run/react-router/pull/12021))\n- `@react-router/dev` - Enable prerendering for resource routes ([#12200](https://github.com/remix-run/react-router/pull/12200))\n- `@react-router/dev` - resolve config directory relative to flat output file structure ([#12187](https://github.com/remix-run/react-router/pull/12187))\n\n### Changes by Package\n\n- [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router/CHANGELOG.md#700)\n- [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-architect/CHANGELOG.md#700)\n- [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-cloudflare/CHANGELOG.md#700)\n- [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-dev/CHANGELOG.md#700)\n- [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-express/CHANGELOG.md#700)\n- [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-fs-routes/CHANGELOG.md#700)\n- [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-node/CHANGELOG.md#700)\n- [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#700)\n- [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-serve/CHANGELOG.md#700)\n\n**Full Changelog**: [`v6.28.0...v7.0.0`](https://github.com/remix-run/react-router/compare/react-router@6.28.0...react-router@7.0.0)\n\n# React Router v6 Releases\n\n## v6.30.3\n\nDate: 2026-01-07\n\n### Security Notice\n\nThis release addresses 1 security vulnerability:\n\n- [XSS via Open Redirects](https://github.com/remix-run/react-router/security/advisories/GHSA-2w69-qvjg-hvjx)\n\n### Patch Changes\n\n- Validate redirect locations ([#14707](https://github.com/remix-run/react-router/pull/14707))\n\n**Full Changelog**: [`v6.30.2...v6.30.3`](https://github.com/remix-run/react-router/compare/react-router@6.30.2...react-router@6.30.3)\n\n## v6.30.2\n\nDate: 2025-11-13\n\n### Security Notice\n\nThis release addresses 1 security vulnerability:\n\n- [Unexpected external redirect via untrusted paths](https://github.com/remix-run/react-router/security/advisories/GHSA-9jcx-v3wj-wh4m)\n\n### Patch Changes\n\n- Normalize double-slashes in `resolvePath` ([#14537](https://github.com/remix-run/react-router/pull/14537))\n\n**Full Changelog**: [`v6.30.1...v6.30.2`](https://github.com/remix-run/react-router/compare/react-router@6.30.1...react-router@6.30.2)\n\n## v6.30.1\n\nDate: 2025-05-20\n\n### Patch Changes\n\n- Partially revert optimization added in `6.29.0` to reduce calls to `matchRoutes` because it surfaced other issues ([#13623](https://github.com/remix-run/react-router/pull/13623))\n- Stop logging invalid warning when `v7_relativeSplatPath` is set to `false` ([#13502](https://github.com/remix-run/react-router/pull/13502))\n\n**Full Changelog**: [`v6.30.0...v6.30.1`](https://github.com/remix-run/react-router/compare/react-router@6.30.0...react-router@6.30.1)\n\n## v6.30.0\n\nDate: 2025-02-27\n\n### Minor Changes\n\n- Add `fetcherKey` as a parameter to `patchRoutesOnNavigation` ([#13109](https://github.com/remix-run/react-router/pull/13109))\n\n### Patch Changes\n\n- Fix regression introduced in `6.29.0` via [#12169](https://github.com/remix-run/react-router/pull/12169) that caused issues navigating to hash routes inside splat routes for applications using Lazy Route Discovery (`patchRoutesOnNavigation`) ([#13108](https://github.com/remix-run/react-router/pull/13108))\n\n**Full Changelog**: [`v6.29.0...v6.30.0`](https://github.com/remix-run/react-router/compare/react-router@6.29.0...react-router@6.30.0)\n\n## v6.29.0\n\nDate: 2025-01-30\n\n### Minor Changes\n\n- Provide the request `signal` as a parameter to `patchRoutesOnNavigation` ([#12900](https://github.com/remix-run/react-router/pull/12900))\n - This can be used to abort any manifest fetches if the in-flight navigation/fetcher is aborted\n\n### Patch Changes\n\n- Do not log v7 deprecation warnings in production builds ([#12794](https://github.com/remix-run/react-router/pull/12794))\n- Properly bubble headers when throwing a `data()` result ([#12845](https://github.com/remix-run/react-router/pull/12845))\n- Optimize route matching by skipping redundant `matchRoutes` calls when possible ([#12169](https://github.com/remix-run/react-router/pull/12169))\n- Strip search parameters from `patchRoutesOnNavigation` `path` param for fetcher calls ([#12899](https://github.com/remix-run/react-router/pull/12899))\n\n**Full Changelog**: [`v6.28.2...v6.29.0`](https://github.com/remix-run/react-router/compare/react-router@6.28.2...react-router@6.29.0)\n\n## v6.28.2\n\nDate: 2025-01-16\n\n### Patch Changes\n\n- Fix manual fetcher `key` usage when not opted into `future.v7_fetcherPersist` ([#12674](https://github.com/remix-run/react-router/pull/12674))\n- Fix issue with fetcher data cleanup in the data layer on fetcher unmount ([#12674](https://github.com/remix-run/react-router/pull/12674))\n\n**Full Changelog**: [`v6.28.1...v6.28.2`](https://github.com/remix-run/react-router/compare/react-router@6.28.1...react-router@6.28.2)\n\n## v6.28.1\n\nDate: 2024-12-20\n\n### Patch Changes\n\n- Allow users to opt out of v7 deprecation warnings by setting flags to `false` ([#12441](https://github.com/remix-run/react-router/pull/12441))\n\n**Full Changelog**: [`v6.28.0...v6.28.1`](https://github.com/remix-run/react-router/compare/react-router@6.28.0...react-router@6.28.1)\n\n## v6.28.0\n\nDate: 2024-11-06\n\n### What's Changed\n\n- In preparation for v7 we've added deprecation warnings for any future flags that you have not yet opted into. Please use the flags to better prepare for eventually upgrading to v7.\n\n### Minor Changes\n\n- Log deprecation warnings for v7 flags ([#11750](https://github.com/remix-run/react-router/pull/11750))\n - Add deprecation warnings to `json`/`defer` in favor of returning raw objects\n - These methods will be removed in React Router v7\n\n### Patch Changes\n\n- Update JSDoc URLs for new website structure (add /v6/ segment) ([#12141](https://github.com/remix-run/react-router/pull/12141))\n\n**Full Changelog**: [`v6.27.0...v6.28.0`](https://github.com/remix-run/react-router/compare/react-router@6.27.0...react-router@6.28.0)\n\n## v6.27.0\n\nDate: 2024-10-11\n\n### What's Changed\n\n#### Stabilized APIs\n\nThis release stabilizes a handful of \"unstable\" APIs in preparation for the [pending](https://x.com/remix_run/status/1841926034868077009) React Router v7 release (see [these](https://remix.run/blog/merging-remix-and-react-router) [posts](https://remix.run/blog/incremental-path-to-react-19) for more info):\n\n- `unstable_dataStrategy` โ†’ `dataStrategy` (`createBrowserRouter` and friends) ([Docs](https://reactrouter.com/v6/routers/create-browser-router#optsdatastrategy))\n- `unstable_patchRoutesOnNavigation` โ†’ `patchRoutesOnNavigation` (`createBrowserRouter` and friends) ([Docs](https://reactrouter.com/v6/routers/create-browser-router#optspatchroutesonnavigation))\n- `unstable_flushSync` โ†’ `flushSync` (`useSubmit`, `fetcher.load`, `fetcher.submit`) ([Docs](https://reactrouter.com/v6/hooks/use-submit#optionsflushsync))\n- `unstable_viewTransition` โ†’ `viewTransition` (``, ``, `useNavigate`, `useSubmit`) ([Docs](https://reactrouter.com/v6/components/link#viewtransition))\n\n### Minor Changes\n\n- Stabilize the `unstable_flushSync` option for navigations and fetchers ([#11989](https://github.com/remix-run/react-router/pull/11989))\n- Stabilize the `unstable_viewTransition` option for navigations and the corresponding `unstable_useViewTransitionState` hook ([#11989](https://github.com/remix-run/react-router/pull/11989))\n- Stabilize `unstable_dataStrategy` ([#11974](https://github.com/remix-run/react-router/pull/11974))\n- Stabilize `unstable_patchRoutesOnNavigation` ([#11973](https://github.com/remix-run/react-router/pull/11973))\n - Add new `PatchRoutesOnNavigationFunctionArgs` type for convenience ([#11967](https://github.com/remix-run/react-router/pull/11967))\n\n### Patch Changes\n\n- Fix bug when submitting to the current contextual route (parent route with an index child) when an `?index` param already exists from a prior submission ([#12003](https://github.com/remix-run/react-router/pull/12003))\n- Fix `useFormAction` bug - when removing `?index` param it would not keep other non-Remix `index` params ([#12003](https://github.com/remix-run/react-router/pull/12003))\n- Fix bug with fetchers not persisting `preventScrollReset` through redirects during concurrent fetches ([#11999](https://github.com/remix-run/react-router/pull/11999))\n- Avoid unnecessary `console.error` on fetcher abort due to back-to-back revalidation calls ([#12050](https://github.com/remix-run/react-router/pull/12050))\n- Fix bugs with `partialHydration` when hydrating with errors ([#12070](https://github.com/remix-run/react-router/pull/12070))\n- Remove internal cache to fix issues with interrupted `patchRoutesOnNavigation` calls ([#12055](https://github.com/remix-run/react-router/pull/12055))\n - โš ๏ธ This may be a breaking change if you were relying on this behavior in the `unstable_` API\n - We used to cache in-progress calls to `patchRoutesOnNavigation` internally so that multiple navigations with the same start/end would only execute the function once and use the same promise\n - However, this approach was at odds with `patch` short circuiting if a navigation was interrupted (and the `request.signal` aborted) since the first invocation's `patch` would no-op\n - This cache also made some assumptions as to what a valid cache key might be - and is oblivious to any other application-state changes that may have occurred\n - So, the cache has been removed because in _most_ cases, repeated calls to something like `import()` for async routes will already be cached automatically - and if not it's easy enough for users to implement this cache in userland\n- Remove internal `discoveredRoutes` FIFO queue from `unstable_patchRoutesOnNavigation` ([#11977](https://github.com/remix-run/react-router/pull/11977))\n - โš ๏ธ This may be a breaking change if you were relying on this behavior in the `unstable_` API\n - This was originally implemented as an optimization but it proved to be a bit too limiting\n - If you need this optimization you can implement your own cache inside `patchRoutesOnNavigation`\n- Fix types for `RouteObject` within `PatchRoutesOnNavigationFunction`'s `patch` method so it doesn't expect agnostic route objects passed to `patch` ([#11967](https://github.com/remix-run/react-router/pull/11967))\n- Expose errors thrown from `patchRoutesOnNavigation` directly to `useRouteError` instead of wrapping them in a 400 `ErrorResponse` instance ([#12111](https://github.com/remix-run/react-router/pull/12111))\n\n**Full Changelog**: [`v6.26.2...v6.27.0`](https://github.com/remix-run/react-router/compare/react-router@6.26.2...react-router@6.27.0)\n\n## v6.26.2\n\nDate: 2024-09-09\n\n### Patch Changes\n\n- Update the `unstable_dataStrategy` API to allow for more advanced implementations ([#11943](https://github.com/remix-run/react-router/pull/11943))\n - โš ๏ธ If you have already adopted `unstable_dataStrategy`, please review carefully as this includes breaking changes to this API\n - Rename `unstable_HandlerResult` to `unstable_DataStrategyResult`\n - Change the return signature of `unstable_dataStrategy` from a parallel array of `unstable_DataStrategyResult[]` (parallel to `matches`) to a key/value object of `routeId => unstable_DataStrategyResult`\n - This allows more advanced control over revalidation behavior because you can opt-into or out-of revalidating data that may not have been revalidated by default (via `match.shouldLoad`)\n - You should now return/throw a result from your `handlerOverride` instead of returning a `DataStrategyResult`\n - The return value (or thrown error) from your `handlerOverride` will be wrapped up into a `DataStrategyResult` and returned fromm `match.resolve`\n - Therefore, if you are aggregating the results of `match.resolve()` into a final results object you should not need to think about the `DataStrategyResult` type\n - If you are manually filling your results object from within your `handlerOverride`, then you will need to assign a `DataStrategyResult` as the value so React Router knows if it's a successful execution or an error (see examples in the documentation for details)\n - Added a new `fetcherKey` parameter to `unstable_dataStrategy` to allow differentiation from navigational and fetcher calls\n- Preserve opted-in view transitions through redirects ([#11925](https://github.com/remix-run/react-router/pull/11925))\n- Preserve pending view transitions through a router revalidation call ([#11917](https://github.com/remix-run/react-router/pull/11917))\n- Fix blocker usage when `blocker.proceed` is called quickly/synchronously ([#11930](https://github.com/remix-run/react-router/pull/11930))\n\n**Full Changelog**: [`v6.26.1...v6.26.2`](https://github.com/remix-run/react-router/compare/react-router@6.26.1...react-router@6.26.2)\n\n## v6.26.1\n\nDate: 2024-08-15\n\n### Patch Changes\n\n- Rename `unstable_patchRoutesOnMiss` to `unstable_patchRoutesOnNavigation` to match new behavior ([#11888](https://github.com/remix-run/react-router/pull/11888))\n- Update `unstable_patchRoutesOnNavigation` logic so that we call the method when we match routes with dynamic param or splat segments in case there exists a higher-scoring static route that we've not yet discovered ([#11883](https://github.com/remix-run/react-router/pull/11883))\n - We also now leverage an internal FIFO queue of previous paths we've already called `unstable_patchRoutesOnNavigation` against so that we don't re-call on subsequent navigations to the same path\n\n**Full Changelog**: [`v6.26.0...v6.26.1`](https://github.com/remix-run/react-router/compare/react-router@6.26.0...react-router@6.26.1)\n\n## v6.26.0\n\nDate: 2024-08-01\n\n### Minor Changes\n\n- Add a new `replace(url, init?)` alternative to `redirect(url, init?)` that performs a `history.replaceState` instead of a `history.pushState` on client-side navigation redirects ([#11811](https://github.com/remix-run/react-router/pull/11811))\n- Add a new `unstable_data()` API for usage with Remix Single Fetch ([#11836](https://github.com/remix-run/react-router/pull/11836))\n - This API is not intended for direct usage in React Router SPA applications\n - It is primarily intended for usage with `createStaticHandler.query()` to allow loaders/actions to return arbitrary data along with custom `status`/`headers` without forcing the serialization of data into a `Response` instance\n - This allows for more advanced serialization tactics via `unstable_dataStrategy` such as serializing via `turbo-stream` in Remix Single Fetch\n - โš ๏ธ This removes the `status` field from `HandlerResult`\n - If you need to return a specific `status` from `unstable_dataStrategy` you should instead do so via `unstable_data()`\n\n### Patch Changes\n\n- Fix internal cleanup of interrupted fetchers to avoid invalid revalidations on navigations ([#11839](https://github.com/remix-run/react-router/pull/11839))\n- Fix initial hydration behavior when using `future.v7_partialHydration` along with `unstable_patchRoutesOnMiss` ([#11838](https://github.com/remix-run/react-router/pull/11838))\n - During initial hydration, `router.state.matches` will now include any partial matches so that we can render ancestor `HydrateFallback` components\n\n**Full Changelog**: [`v6.25.1...v6.26.0`](https://github.com/remix-run/react-router/compare/react-router@6.25.1...react-router@6.26.0)\n\n## v6.25.1\n\nDate: 2024-07-17\n\n### Patch Changes\n\n- Memoize some `RouterProvider` internals to reduce unnecessary re-renders ([#11803](https://github.com/remix-run/react-router/pull/11803))\n\n**Full Changelog**: [`v6.25.0...v6.25.1`](https://github.com/remix-run/react-router/compare/react-router@6.25.0...react-router@6.25.1)\n\n## v6.25.0\n\nDate: 2024-07-16\n\n### What's Changed\n\n#### Stabilized `v7_skipActionErrorRevalidation`\n\nThis release stabilizes the `future.unstable_skipActionErrorRevalidation` flag into [`future.v7_skipActionErrorRevalidation`](https://reactrouter.com/v6/upgrading/future#v7_skipactionstatusrevalidation) in preparation for the upcoming React Router v7 release.\n\n- When this flag is enabled, actions that return/throw a `4xx/5xx` `Response` will not trigger a revalidation by default\n- This also stabilizes `shouldRevalidate`'s `unstable_actionStatus` parameter to `actionStatus`\n\n### Minor Changes\n\n- Stabilize `future.unstable_skipActionErrorRevalidation` as `future.v7_skipActionErrorRevalidation` ([#11769](https://github.com/remix-run/react-router/pull/11769))\n\n### Patch Changes\n\n- Fix regression and properly decode paths inside `useMatch` so matches/params reflect decoded params ([#11789](https://github.com/remix-run/react-router/pull/11789))\n- Fix bubbling of errors thrown from `unstable_patchRoutesOnMiss` ([#11786](https://github.com/remix-run/react-router/pull/11786))\n- Fix hydration in SSR apps using `unstable_patchRoutesOnMiss` that matched a splat route on the server ([#11790](https://github.com/remix-run/react-router/pull/11790))\n\n**Full Changelog**: [`v6.24.1...v6.25.0`](https://github.com/remix-run/react-router/compare/react-router@6.24.1...react-router@6.25.0)\n\n## v6.24.1\n\nDate: 2024-07-03\n\n### Patch Changes\n\n- Remove `polyfill.io` reference from warning message because the domain was sold and has since been determined to serve malware ([#11741](https://github.com/remix-run/react-router/pull/11741))\n - See https://sansec.io/research/polyfill-supply-chain-attack\n- Export `NavLinkRenderProps` type for easier typing of custom `NavLink` callback ([#11553](https://github.com/remix-run/react-router/pull/11553))\n- When using `future.v7_relativeSplatPath`, properly resolve relative paths in splat routes that are children of pathless routes ([#11633](https://github.com/remix-run/react-router/pull/11633))\n- Fog of War (unstable): Trigger a new `router.routes` identity/reflow during route patching ([#11740](https://github.com/remix-run/react-router/pull/11740))\n- Fog of War (unstable): Fix initial matching when a splat route matches ([#11759](https://github.com/remix-run/react-router/pull/11759))\n\n**Full Changelog**: [`v6.24.0...v6.24.1`](https://github.com/remix-run/react-router/compare/react-router@6.24.0...react-router@6.24.1)\n\n## v6.24.0\n\nDate: 2024-06-24\n\n### What's Changed\n\n#### Lazy Route Discovery (a.k.a. \"Fog of War\")\n\nWe're really excited to release our new API for \"Lazy Route Discovery\" in `v6.24.0`! For some background information, please check out the original [RFC](https://github.com/remix-run/react-router/discussions/11113). The **tl;dr;** is that ever since we introduced the Data APIs in v6.4 via ``, we've been a little bummed that one of the tradeoffs was the lack of a compelling code-splitting story mirroring what we had in the ``/`` apps. We took a baby-step towards improving that story with `route.lazy` in `v6.9.0`, but with `v6.24.0` we've gone the rest of the way.\n\nWith \"Fog of War\", you can now load portions of the route tree lazily via the new `unstable_patchRoutesOnMiss` option passed to `createBrowserRouter` (and it's memory/hash counterparts). This gives you a way to hook into spots where React Router is unable to match a given path and patch new routes into the route tree during the navigation (or fetcher call).\n\nHere's a very small example, but please refer to the [documentation](https://reactrouter.com/v6/routers/create-browser-router#optsunstable_patchroutesonmiss) for more information and use cases:\n\n```js\nconst router = createBrowserRouter(\n [\n {\n id: \"root\",\n path: \"/\",\n Component: RootComponent,\n },\n ],\n {\n async unstable_patchRoutesOnMiss({ path, patch }) {\n if (path === \"/a\") {\n // Load the `a` route (`{ path: 'a', Component: A }`)\n let route = await getARoute();\n // Patch the `a` route in as a new child of the `root` route\n patch(\"root\", [route]);\n }\n },\n },\n);\n```\n\n### Minor Changes\n\n- Add support for Lazy Route Discovery (a.k.a. \"Fog of War\") ([#11626](https://github.com/remix-run/react-router/pull/11626))\n\n### Patch Changes\n\n- Fix `fetcher.submit` types - remove incorrect `navigate`/`fetcherKey`/`unstable_viewTransition` options because they are only relevant for `useSubmit` ([#11631](https://github.com/remix-run/react-router/pull/11631))\n- Allow falsy `location.state` values passed to `` ([#11495](https://github.com/remix-run/react-router/pull/11495))\n\n**Full Changelog**: [`v6.23.1...v6.24.0`](https://github.com/remix-run/react-router/compare/react-router@6.23.1...react-router@6.24.0)\n\n## v6.23.1\n\nDate: 2024-05-10\n\n### Patch Changes\n\n- Allow `undefined` to be resolved through `` ([#11513](https://github.com/remix-run/react-router/pull/11513))\n- Add defensive `document` check when checking for `document.startViewTransition` availability ([#11544](https://github.com/remix-run/react-router/pull/11544))\n- Change the `react-router-dom/server` import back to `react-router-dom` instead of `index.ts` ([#11514](https://github.com/remix-run/react-router/pull/11514))\n- `@remix-run/router` - Support `unstable_dataStrategy` on `staticHandler.queryRoute` ([#11515](https://github.com/remix-run/react-router/pull/11515))\n\n**Full Changelog**: [`v6.23.0...v6.23.1`](https://github.com/remix-run/react-router/compare/react-router@6.23.0...react-router@6.23.1)\n\n## v6.23.0\n\nDate: 2024-04-23\n\n### What's Changed\n\n#### Data Strategy (unstable)\n\nThe new `unstable_dataStrategy` API is a low-level API designed for advanced use-cases where you need to take control over the data strategy for your `loader`/`action` functions. The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix [\"Single Fetch\"](https://remix.run/docs/guides/single-fetch), user-land middleware/context APIs, automatic loader caching, and more. Please see the [docs](https://reactrouter.com/v6/routers/create-browser-router#unstable_datastrategy) for more information.\n\n**Note:** This is a low-level API intended for advanced use-cases. This overrides React Router's internal handling of `loader`/`action` execution, and if done incorrectly will break your app code. Please use with caution and perform the appropriate testing.\n\n#### Skip Action Error Revalidation (unstable)\n\nCurrently, all active `loader`'s revalidate after any `action` submission, regardless of the `action` result. However, in the majority of cases a `4xx`/`5xx` response from an `action` means that no data was actually changed and the revalidation is unnecessary. We've introduced a new `future.unstable_skipActionErrorRevalidation` flag that changes the behavior here, and we plan to make this the default in future version of React Router.\n\nWith this flag enabled, `action`'s that return/throw a `4xx`/`5xx` response status will no longer automatically revalidate. If you need to revalidate after a `4xx`/`5xx` result with this flag enabled, you can still do that via returning `true` from `shouldRevalidate` - which now also receives a new `unstable_actionStatus` argument alongside `actionResult` so you can make decision based on the status of the `action` response without having to encode it into the action data.\n\n### Minor Changes\n\n- Add a new `unstable_dataStrategy` configuration option ([#11098](https://github.com/remix-run/react-router/pull/11098), [#11377](https://github.com/remix-run/react-router/pull/11377))\n- `@remix-run/router` - Add a new `future.unstable_skipActionRevalidation` future flag ([#11098](https://github.com/remix-run/react-router/pull/11098))\n- `@remix-run/router` - SSR: Added a new `skipLoaderErrorBubbling` options to the `staticHandler.query` method to disable error bubbling by the static handler for use in Remix's Single Fetch implementation ([#11098](https://github.com/remix-run/react-router/pull/11098), ([#11377](https://github.com/remix-run/react-router/pull/11377)))\n\n**Full Changelog**: [`v6.22.3...v6.23.0`](https://github.com/remix-run/react-router/compare/react-router@6.22.3...react-router@6.23.0)\n\n## v6.22.3\n\nDate: 2024-03-07\n\n### Patch Changes\n\n- Fix a `future.v7_partialHydration` bug that would re-run loaders below the boundary on hydration if SSR loader errors bubbled to a parent boundary ([#11324](https://github.com/remix-run/react-router/pull/11324))\n- Fix a `future.v7_partialHydration` bug that would consider the router uninitialized if a route did not have a loader ([#11325](https://github.com/remix-run/react-router/pull/11325))\n\n**Full Changelog**: [`v6.22.2...v6.22.3`](https://github.com/remix-run/react-router/compare/react-router@6.22.2...react-router@6.22.3)\n\n## v6.22.2\n\nDate: 2024-02-28\n\n### Patch Changes\n\n- Preserve hydrated errors during partial hydration runs ([#11305](https://github.com/remix-run/react-router/pull/11305))\n\n**Full Changelog**: [`v6.22.1...v6.22.2`](https://github.com/remix-run/react-router/compare/react-router@6.22.1...react-router@6.22.2)\n\n## v6.22.1\n\nDate: 2024-02-16\n\n### Patch Changes\n\n- Fix encoding/decoding issues with pre-encoded dynamic parameter values ([#11199](https://github.com/remix-run/react-router/pull/11199))\n\n**Full Changelog**: [`v6.22.0...v6.22.1`](https://github.com/remix-run/react-router/compare/react-router@6.22.0...react-router@6.22.1)\n\n## v6.22.0\n\nDate: 2024-02-01\n\n### What's Changed\n\n#### Core Web Vitals Technology Report Flag\n\nIn 2021, the HTTP Archive launched the [Core Web Vitals Technology Report dashboard](https://discuss.httparchive.org/t/new-dashboard-the-core-web-vitals-technology-report/2178):\n\n> By combining the powers of real-user experiences in the Chrome UX Report 26 (CrUX) dataset with web technology detections in HTTP Archive 30, we can get a glimpse into how architectural decisions like choices of CMS platform or JavaScript framework play a role in sitesโ€™ CWV performance.\n\nThey use a tool called [`wappalyzer`](https://github.com/HTTPArchive/wappalyzer) to identify what technologies a given website is using by looking for certain scripts, global JS variables, or other identifying characteristics. For example, for Remix applications, they [look for the global `__remixContext`](https://github.com/HTTPArchive/wappalyzer/blob/c2a24ee7c2d07bf9c521f02584ae2dcf603ac0b7/src/technologies/r.json#L1328) variable to identify that a website is using Remix.\n\nIt was brought to our attention that React Router was unable to be reliably identified because there are no identifying global aspects. They are currently [looking for external scripts with `react-router`](https://github.com/HTTPArchive/wappalyzer/blob/c2a24ee7c2d07bf9c521f02584ae2dcf603ac0b7/src/technologies/r.json#L637) in the name. This will identify sites using React Router from a CDN such as `unpkg` - but it will miss the **vast** majority of sites that are installing React Router from the npm registry and bundling it into their JS files. This results in [drastically under-reporting](https://lookerstudio.google.com/s/pixHkNmGbN4) the usage of React Router on the web.\n\nStarting with version `6.22.0`, sites using `react-router-dom` will begin adding a `window.__reactRouterVersion` variable that will be set to a string value of the SemVer major version number (i.e., `window.__reactRouterVersion = \"6\";`) so that they can be properly identified.\n\n### Minor Changes\n\n- Include a `window.__reactRouterVersion` for CWV Report detection ([#11222](https://github.com/remix-run/react-router/pull/11222))\n- Add a `createStaticHandler` `future.v7_throwAbortReason` flag to throw `request.signal.reason` (defaults to a `DOMException`) when a request is aborted instead of an `Error` such as `new Error(\"query() call aborted: GET /path\")` ([#11104](https://github.com/remix-run/react-router/pull/11104))\n - Please note that `DOMException` was added in Node v17 so you will not get a `DOMException` on Node 16 and below.\n\n### Patch Changes\n\n- Respect the `ErrorResponse` status code if passed to `getStaticContextFormError` ([#11213](https://github.com/remix-run/react-router/pull/11213))\n\n**Full Changelog**: [`v6.21.3...v6.22.0`](https://github.com/remix-run/react-router/compare/react-router@6.21.3...react-router@6.22.0)\n\n## v6.21.3\n\nDate: 2024-01-18\n\n### Patch Changes\n\n- Fix `NavLink` `isPending` when a `basename` is used ([#11195](https://github.com/remix-run/react-router/pull/11195))\n- Remove leftover `unstable_` prefix from `Blocker`/`BlockerFunction` types ([#11187](https://github.com/remix-run/react-router/pull/11187))\n\n**Full Changelog**: [`v6.21.2...v6.21.3`](https://github.com/remix-run/react-router/compare/react-router@6.21.2...react-router@6.21.3)\n\n## v6.21.2\n\nDate: 2024-01-11\n\n### Patch Changes\n\n- Leverage `useId` for internal fetcher keys when available ([#11166](https://github.com/remix-run/react-router/pull/11166))\n- Fix bug where dashes were not picked up in dynamic parameter names ([#11160](https://github.com/remix-run/react-router/pull/11160))\n- Do not attempt to deserialize empty JSON responses ([#11164](https://github.com/remix-run/react-router/pull/11164))\n\n**Full Changelog**: [`v6.21.1...v6.21.2`](https://github.com/remix-run/react-router/compare/react-router@6.21.1...react-router@6.21.2)\n\n## v6.21.1\n\nDate: 2023-12-21\n\n### Patch Changes\n\n- Fix bug with `route.lazy` not working correctly on initial SPA load when `v7_partialHydration` is specified ([#11121](https://github.com/remix-run/react-router/pull/11121))\n- Fix bug preventing revalidation from occurring for persisted fetchers unmounted during the `submitting` phase ([#11102](https://github.com/remix-run/react-router/pull/11102))\n- De-dup relative path logic in `resolveTo` ([#11097](https://github.com/remix-run/react-router/pull/11097))\n\n**Full Changelog**: [`v6.21.0...v6.21.1`](https://github.com/remix-run/react-router/compare/react-router@6.21.0...react-router@6.21.1)\n\n## v6.21.0\n\nDate: 2023-12-13\n\n### What's Changed\n\n#### `future.v7_relativeSplatPath`\n\nWe fixed a splat route path-resolution bug in `6.19.0`, but later determined a large number of applications were relying on the buggy behavior, so we reverted the fix in `6.20.1` (see [#10983](https://github.com/remix-run/react-router/issues/10983), [#11052](https://github.com/remix-run/react-router/issues/11052), [#11078](https://github.com/remix-run/react-router/issues/11078)).\n\nThe buggy behavior is that the default behavior when resolving relative paths inside a splat route would _ignore_ any splat (`*`) portion of the current route path. When the future flag is enabled, splat portions are included in relative path logic within splat routes.\n\nFor more information, please refer to the [`useResolvedPath` docs](https://reactrouter.com/v6/hooks/use-resolved-path#splat-paths) and/or the [detailed changelog entry](https://github.com/remix-run/react-router/blob/main/packages/react-router-dom/CHANGELOG.md#6210).\n\n#### Partial Hydration\n\nWe added a new `future.v7_partialHydration` future flag for the `@remix-run/router` that enables partial hydration of a data router when Server-Side Rendering. This allows you to provide `hydrationData.loaderData` that has values for _some_ initially matched route loaders, but not all. When this flag is enabled, the router will call `loader` functions for routes that do not have hydration loader data during `router.initialize()`, and it will render down to the deepest provided `HydrateFallback` (up to the first route without hydration data) while it executes the unhydrated routes. ([#11033](https://github.com/remix-run/react-router/pull/11033))\n\n### Minor Changes\n\n- Add a new `future.v7_relativeSplatPath` flag to implement a breaking bug fix to relative routing when inside a splat route. ([#11087](https://github.com/remix-run/react-router/pull/11087))\n- Add a new `future.v7_partialHydration` future flag that enables partial hydration of a data router when Server-Side Rendering ([#11033](https://github.com/remix-run/react-router/pull/11033))\n\n### Patch Changes\n\n- Properly handle falsy error values in `ErrorBoundary`'s ([#11071](https://github.com/remix-run/react-router/pull/11071))\n- Catch and bubble errors thrown when trying to unwrap responses from `loader`/`action` functions ([#11061](https://github.com/remix-run/react-router/pull/11061))\n- Fix `relative=\"path\"` issue when rendering `Link`/`NavLink` outside of matched routes ([#11062](https://github.com/remix-run/react-router/pull/11062))\n\n**Full Changelog**: [`v6.20.1...v6.21.0`](https://github.com/remix-run/react-router/compare/react-router@6.20.1...react-router@6.21.0)\n\n## v6.20.1\n\nDate: 2023-12-01\n\n### Patch Changes\n\n- Revert the `useResolvedPath` fix for splat routes due to a large number of applications that were relying on the buggy behavior (see [#11052](https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329)) ([#11078](https://github.com/remix-run/react-router/pull/11078))\n - We plan to re-introduce this fix behind a future flag in the next minor version (see [this comment](https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329))\n - This fix was included in versions `6.19.0` and `6.20.0`. If you are upgrading from `6.18.0` or earlier, you would not have been impacted by this fix.\n\n**Full Changelog**: [`v6.20.0...v6.20.1`](https://github.com/remix-run/react-router/compare/react-router@6.20.0...react-router@6.20.1)\n\n## v6.20.0\n\nDate: 2023-11-22\n\n> [!WARNING]\n> Please use version `6.20.1` or later instead of `6.20.0`. We discovered that a large number of apps were relying on buggy behavior that was fixed in this release ([#11045](https://github.com/remix-run/react-router/pull/11045)). We reverted the fix in `6.20.1` and will be re-introducing it behind a future flag in a subsequent release. See [#11052](https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329) for more details.\n\n### Minor Changes\n\n- Export the `PathParam` type from the public API ([#10719](https://github.com/remix-run/react-router/pull/10719))\n\n### Patch Changes\n\n- Do not revalidate unmounted fetchers when `v7_fetcherPersist` is enabled ([#11044](https://github.com/remix-run/react-router/pull/11044))\n- Fix bug with `resolveTo` path resolution in splat routes ([#11045](https://github.com/remix-run/react-router/pull/11045))\n - This is a follow up to [#10983](https://github.com/remix-run/react-router/pull/10983) to handle the few other code paths using `getPathContributingMatches`\n - This removes the `UNSAFE_getPathContributingMatches` export from `@remix-run/router` since we no longer need this in the `react-router`/`react-router-dom` layers\n\n**Full Changelog**: [`v6.19.0...v6.20.0`](https://github.com/remix-run/react-router/compare/react-router@6.19.0...react-router@6.20.0)\n\n## v6.19.0\n\nDate: 2023-11-16\n\n> [!WARNING]\n> Please use version `6.20.1` or later instead of `6.19.0`. We discovered that a large number of apps were relying on buggy behavior that was fixed in this release ([#10983](https://github.com/remix-run/react-router/pull/10983)). We reverted the fix in `6.20.1` and will be re-introducing it behind a future flag in a subsequent release. See [#11052](https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329) for more details.\n\n### What's Changed\n\n#### `unstable_flushSync` API\n\nThis release brings a new `unstable_flushSync` option to the imperative APIs (`useSubmit`, `useNavigate`, `fetcher.submit`, `fetcher.load`) to let users opt-into synchronous DOM updates for pending/optimistic UI.\n\n```js\nfunction handleClick() {\n submit(data, { flushSync: true });\n // Everything is flushed to the DOM so you can focus/scroll to your pending/optimistic UI\n setFocusAndOrScrollToNewlyAddedThing();\n}\n```\n\n### Minor Changes\n\n- Add `unstable_flushSync` option to `useNavigate`/`useSubmit`/`fetcher.load`/`fetcher.submit` to opt-out of `React.startTransition` and into `ReactDOM.flushSync` for state updates ([#11005](https://github.com/remix-run/react-router/pull/11005))\n- Remove the `unstable_` prefix from the [`useBlocker`](https://reactrouter.com/v6/hooks/use-blocker) hook as it's been in use for enough time that we are confident in the API ([#10991](https://github.com/remix-run/react-router/pull/10991))\n - We do not plan to remove the prefix from `unstable_usePrompt` due to differences in how browsers handle `window.confirm` that prevent React Router from guaranteeing consistent/correct behavior\n\n### Patch Changes\n\n- Fix `useActionData` so it returns proper contextual action data and not _any_ action data in the tree ([#11023](https://github.com/remix-run/react-router/pull/11023))\n- Fix bug in `useResolvedPath` that would cause `useResolvedPath(\".\")` in a splat route to lose the splat portion of the URL path. ([#10983](https://github.com/remix-run/react-router/pull/10983))\n - โš ๏ธ This fixes a quite long-standing bug specifically for `\".\"` paths inside a splat route which incorrectly dropped the splat portion of the URL. If you are relative routing via `\".\"` inside a splat route in your application you should double check that your logic is not relying on this buggy behavior and update accordingly.\n- Fix issue where a changing fetcher `key` in a `useFetcher` that remains mounted wasn't getting picked up ([#11009](https://github.com/remix-run/react-router/pull/11009))\n- Fix `useFormAction` which was incorrectly inheriting the `?index` query param from child route `action` submissions ([#11025](https://github.com/remix-run/react-router/pull/11025))\n- Fix `NavLink` `active` logic when `to` location has a trailing slash ([#10734](https://github.com/remix-run/react-router/pull/10734))\n- Fix types so `unstable_usePrompt` can accept a `BlockerFunction` in addition to a `boolean` ([#10991](https://github.com/remix-run/react-router/pull/10991))\n- Fix `relative=\"path\"` bug where relative path calculations started from the full location pathname, instead of from the current contextual route pathname. ([#11006](https://github.com/remix-run/react-router/pull/11006))\n\n ```jsx\n \n }>\n \n \n ;\n\n function Component() {\n return (\n <>\n {/* This is now correctly relative to /a/b, not /a/b/c */}\n \n \n \n );\n }\n ```\n\n**Full Changelog**: [`6.18.0...6.19.0`](https://github.com/remix-run/react-router/compare/react-router@6.18.0...react-router@6.19.0)\n\n## v6.18.0\n\nDate: 2023-10-31\n\n### What's Changed\n\n#### New Fetcher APIs\n\nPer this [RFC](https://github.com/remix-run/remix/discussions/7698), we've introduced some new APIs that give you more granular control over your fetcher behaviors.\n\n- You may now specify your own fetcher identifier via `useFetcher({ key: string })`, which allows you to access the same fetcher instance from different components in your application without prop-drilling\n- Fetcher keys are now exposed on the fetchers returned from `useFetchers` so that they can be looked up by `key`\n- `Form` and `useSubmit` now support optional `navigate`/`fetcherKey` props/params to allow kicking off a fetcher submission under the hood with an optionally user-specified `key`\n - ``\n - `submit(data, { method: \"post\", navigate: false, fetcherKey: \"my-key\" })`\n - Invoking a fetcher in this way is ephemeral and stateless\n - If you need to access the state of one of these fetchers, you will need to leverage `useFetchers()` or `useFetcher({ key })` to look it up elsewhere\n\n#### Persistence Future Flag (`future.v7_fetcherPersist`)\n\nPer the same [RFC](https://github.com/remix-run/remix/discussions/7698) as above, we've introduced a new `future.v7_fetcherPersist` flag that allows you to opt-into the new fetcher persistence/cleanup behavior. Instead of being immediately cleaned up on unmount, fetchers will persist until they return to an `idle` state. This makes pending/optimistic UI _much_ easier in scenarios where the originating fetcher needs to unmount.\n\n- This is sort of a long-standing bug fix as the `useFetchers()` API was always supposed to only reflect **in-flight** fetcher information for pending/optimistic UI -- it was not intended to reflect fetcher data or hang onto fetchers after they returned to an `idle` state\n- Keep an eye out for the following specific behavioral changes when opting into this flag and check your app for compatibility:\n - Fetchers that complete _while still mounted_ will no longer appear in `useFetchers()` after completion - they served no purpose in there since you can access the data via `useFetcher().data`\n - Fetchers that previously unmounted _while in-flight_ will not be immediately aborted and will instead be cleaned up once they return to an `idle` state\n - They will remain exposed via `useFetchers` while in-flight so you can still access pending/optimistic data after unmount\n - If a fetcher is no longer mounted when it completes, then it's result will not be post processed - e.g., redirects will not be followed and errors will not bubble up in the UI\n - However, if a fetcher was re-mounted elsewhere in the tree using the same `key`, then it's result will be processed, even if the originating fetcher was unmounted\n\n### Minor Changes\n\n- Add fetcher `key` APIs and `navigate=false` options ([#10960](https://github.com/remix-run/react-router/pull/10960))\n- Add `future.v7_fetcherPersist` flag ([#10962](https://github.com/remix-run/react-router/pull/10962))\n- Add support for optional path segments in `matchPath` ([#10768](https://github.com/remix-run/react-router/pull/10768))\n\n### Patch Changes\n\n- Fix the `future` prop on `BrowserRouter`, `HashRouter` and `MemoryRouter` so that it accepts a `Partial` instead of requiring all flags to be included ([#10962](https://github.com/remix-run/react-router/pull/10962))\n- Fix `router.getFetcher`/`router.deleteFetcher` type definitions which incorrectly specified `key` as an optional parameter ([#10960](https://github.com/remix-run/react-router/pull/10960))\n\n**Full Changelog**: [`6.17.0...6.18.0`](https://github.com/remix-run/react-router/compare/react-router@6.17.0...react-router@6.18.0)\n\n## v6.17.0\n\nDate: 2023-10-16\n\n### What's Changed\n\n#### View Transitions ๐Ÿš€\n\nWe're excited to release experimental support for the [View Transitions API](https://developer.mozilla.org/en-US/docs/Web/API/ViewTransition) in React Router! You can now trigger navigational DOM updates to be wrapped in `document.startViewTransition` to enable CSS animated transitions on SPA navigations in your application.\n\nThe simplest approach to enabling a View Transition in your React Router app is via the new [``](https://reactrouter.com/v6/components/link#unstable_viewtransition) prop. This will cause the navigation DOM update to be wrapped in `document.startViewTransition` which will enable transitions for the DOM update. Without any additional CSS styles, you'll get a basic cross-fade animation for your page.\n\nIf you need to apply more fine-grained styles for your animations, you can leverage the [`unstable_useViewTransitionState`](https://reactrouter.com/v6/hooks/use-view-transition-state) hook which will tell you when a transition is in progress and you can use that to apply classes or styles:\n\n```jsx\nfunction ImageLink(to, src, alt) {\n const isTransitioning = unstable_useViewTransitionState(to);\n return (\n \n \n \n );\n}\n```\n\nYou can also use the [``](https://reactrouter.com/v6/components/nav-link#unstable_viewtransition) shorthand which will manage the hook usage for you and automatically add a `transitioning` class to the `` during the transition:\n\n```css\na.transitioning img {\n view-transition-name: \"image-expand\";\n}\n```\n\n```jsx\n\n {alt}\n\n```\n\nFor an example usage of View Transitions, check out [our fork](https://github.com/brophdawg11/react-router-records) of the awesome [Astro Records](https://github.com/Charca/astro-records) demo.\n\nFor more information on using the View Transitions API, please refer to the [Smooth and simple transitions with the View Transitions API](https://developer.chrome.com/docs/web-platform/view-transitions/) guide from the Google Chrome team.\n\n### Minor Changes\n\n- Add support for view transitions ([#10916](https://github.com/remix-run/react-router/pull/10916))\n\n### Patch Changes\n\n- Log a warning and fail gracefully in `ScrollRestoration` when `sessionStorage` is unavailable ([#10848](https://github.com/remix-run/react-router/pull/10848))\n- Fix `RouterProvider` `future` prop type to be a `Partial` so that not all flags must be specified ([#10900](https://github.com/remix-run/react-router/pull/10900))\n- Allow 404 detection to leverage root route error boundary if path contains a URL segment ([#10852](https://github.com/remix-run/react-router/pull/10852))\n- Fix `ErrorResponse` type to avoid leaking internal field ([#10876](https://github.com/remix-run/react-router/pull/10876))\n\n**Full Changelog**: [`6.16.0...6.17.0`](https://github.com/remix-run/react-router/compare/react-router@6.16.0...react-router@6.17.0)\n\n## v6.16.0\n\nDate: 2023-09-13\n\n### Minor Changes\n\n- In order to move towards stricter TypeScript support in the future, we're aiming to replace current usages of `any` with `unknown` on exposed typings for user-provided data. To do this in Remix v2 without introducing breaking changes in React Router v6, we have added generics to a number of shared types. These continue to default to `any` in React Router and are overridden with `unknown` in Remix. In React Router v7 we plan to move these to `unknown` as a breaking change. ([#10843](https://github.com/remix-run/react-router/pull/10843))\n - `Location` now accepts a generic for the `location.state` value\n - `ActionFunctionArgs`/`ActionFunction`/`LoaderFunctionArgs`/`LoaderFunction` now accept a generic for the `context` parameter (only used in SSR usages via `createStaticHandler`)\n - The return type of `useMatches` (now exported as `UIMatch`) accepts generics for `match.data` and `match.handle` - both of which were already set to `unknown`\n- Move the `@private` class export `ErrorResponse` to an `UNSAFE_ErrorResponseImpl` export since it is an implementation detail and there should be no construction of `ErrorResponse` instances in userland. This frees us up to export a `type ErrorResponse` which correlates to an instance of the class via `InstanceType`. Userland code should only ever be using `ErrorResponse` as a type and should be type-narrowing via `isRouteErrorResponse`. ([#10811](https://github.com/remix-run/react-router/pull/10811))\n- Export `ShouldRevalidateFunctionArgs` interface ([#10797](https://github.com/remix-run/react-router/pull/10797))\n- Removed private/internal APIs only required for the Remix v1 backwards compatibility layer and no longer needed in Remix v2 (`_isFetchActionRedirect`, `_hasFetcherDoneAnything`) ([#10715](https://github.com/remix-run/react-router/pull/10715))\n\n### Patch Changes\n\n- Properly encode rendered URIs in server rendering to avoid hydration errors ([#10769](https://github.com/remix-run/react-router/pull/10769))\n- Add method/url to error message on aborted `query`/`queryRoute` calls ([#10793](https://github.com/remix-run/react-router/pull/10793))\n- Fix a race-condition with loader/action-thrown errors on `route.lazy` routes ([#10778](https://github.com/remix-run/react-router/pull/10778))\n- Fix type for `actionResult` on the arguments object passed to `shouldRevalidate` ([#10779](https://github.com/remix-run/react-router/pull/10779))\n\n**Full Changelog**: [`v6.15.0...v6.16.0`](https://github.com/remix-run/react-router/compare/react-router@6.15.0...react-router@6.16.0)\n\n## v6.15.0\n\nDate: 2023-08-10\n\n### Minor Changes\n\n- Add's a new `redirectDocument()` function which allows users to specify that a redirect from a `loader`/`action` should trigger a document reload (via `window.location`) instead of attempting to navigate to the redirected location via React Router ([#10705](https://github.com/remix-run/react-router/pull/10705))\n\n### Patch Changes\n\n- Ensure `useRevalidator` is referentially stable across re-renders if revalidations are not actively occurring ([#10707](https://github.com/remix-run/react-router/pull/10707))\n- Ensure hash history always includes a leading slash on hash pathnames ([#10753](https://github.com/remix-run/react-router/pull/10753))\n- Fixes an edge-case affecting web extensions in Firefox that use `URLSearchParams` and the `useSearchParams` hook ([#10620](https://github.com/remix-run/react-router/pull/10620))\n- Reorder effects in `unstable_usePrompt` to avoid throwing an exception if the prompt is unblocked and a navigation is performed synchronously ([#10687](https://github.com/remix-run/react-router/pull/10687), [#10718](https://github.com/remix-run/react-router/pull/10718))\n- SSR: Do not include hash in `useFormAction()` for unspecified actions since it cannot be determined on the server and causes hydration issues ([#10758](https://github.com/remix-run/react-router/pull/10758))\n- SSR: Fix an issue in `queryRoute` that was not always identifying thrown `Response` instances ([#10717](https://github.com/remix-run/react-router/pull/10717))\n- `react-router-native`: Update `@ungap/url-search-params` dependency from `^0.1.4` to `^0.2.2` ([#10590](https://github.com/remix-run/react-router/pull/10590))\n\n**Full Changelog**: [`v6.14.2...v6.15.0`](https://github.com/remix-run/react-router/compare/react-router@6.14.2...react-router@6.15.0)\n\n## v6.14.2\n\nDate: 2023-07-17\n\n### Patch Changes\n\n- Add missing `` prop to populate `history.state` on submission navigations ([#10630](https://github.com/remix-run/react-router/pull/10630))\n- Trigger an error if a `defer` promise resolves/rejects with `undefined` in order to match the behavior of loaders and actions which must return a value or `null` ([#10690](https://github.com/remix-run/react-router/pull/10690))\n- Properly handle fetcher redirects interrupted by normal navigations ([#10674](https://github.com/remix-run/react-router/pull/10674))\n- Initial-load fetchers should not automatically revalidate on GET navigations ([#10688](https://github.com/remix-run/react-router/pull/10688))\n- Properly decode element id when emulating hash scrolling via `` ([#10682](https://github.com/remix-run/react-router/pull/10682))\n- Typescript: Enhance the return type of `Route.lazy` to prohibit returning an empty object ([#10634](https://github.com/remix-run/react-router/pull/10634))\n- SSR: Support proper hydration of `Error` subclasses such as `ReferenceError`/`TypeError` ([#10633](https://github.com/remix-run/react-router/pull/10633))\n\n**Full Changelog**: [`v6.14.1...v6.14.2`](https://github.com/remix-run/react-router/compare/react-router@6.14.1...react-router@6.14.2)\n\n## v6.14.1\n\nDate: 2023-06-30\n\n### Patch Changes\n\n- Fix loop in `unstable_useBlocker` when used with an unstable blocker function ([#10652](https://github.com/remix-run/react-router/pull/10652))\n- Fix issues with reused blockers on subsequent navigations ([#10656](https://github.com/remix-run/react-router/pull/10656))\n- Updated dependencies:\n - `@remix-run/router@1.7.1`\n\n**Full Changelog**: [`v6.14.0...v6.14.1`](https://github.com/remix-run/react-router/compare/react-router@6.14.0...react-router@6.14.1)\n\n## v6.14.0\n\nDate: 2023-06-23\n\n### What's Changed\n\n#### JSON/Text Submissions\n\n`6.14.0` adds support for JSON and Text submissions via `useSubmit`/`fetcher.submit` since it's not always convenient to have to serialize into `FormData` if you're working in a client-side SPA. To opt-into these encodings you just need to specify the proper `formEncType`:\n\n**Opt-into `application/json` encoding:**\n\n```js\nfunction Component() {\n let navigation = useNavigation();\n let submit = useSubmit();\n submit({ key: \"value\" }, { method: \"post\", encType: \"application/json\" });\n // navigation.formEncType => \"application/json\"\n // navigation.json => { key: \"value\" }\n}\n\nasync function action({ request }) {\n // request.headers.get(\"Content-Type\") => \"application/json\"\n // await request.json() => { key: \"value\" }\n}\n```\n\n**Opt-into `text/plain` encoding:**\n\n```js\nfunction Component() {\n let navigation = useNavigation();\n let submit = useSubmit();\n submit(\"Text submission\", { method: \"post\", encType: \"text/plain\" });\n // navigation.formEncType => \"text/plain\"\n // navigation.text => \"Text submission\"\n}\n\nasync function action({ request }) {\n // request.headers.get(\"Content-Type\") => \"text/plain\"\n // await request.text() => \"Text submission\"\n}\n```\n\n**โš ๏ธ Default Behavior Will Change in v7**\n\nPlease note that to avoid a breaking change, the default behavior will still encode a simple key/value JSON object into a `FormData` instance:\n\n```jsx\nfunction Component() {\n let navigation = useNavigation();\n let submit = useSubmit();\n submit({ key: \"value\" }, { method: \"post\" });\n // navigation.formEncType => \"application/x-www-form-urlencoded\"\n // navigation.formData => FormData instance\n}\n\nasync function action({ request }) {\n // request.headers.get(\"Content-Type\") => \"application/x-www-form-urlencoded\"\n // await request.formData() => FormData instance\n}\n```\n\nThis behavior will likely change in v7 so it's best to make any JSON object submissions explicit with `formEncType: \"application/x-www-form-urlencoded\"` or `formEncType: \"application/json\"` to ease your eventual v7 migration path.\n\n### Minor Changes\n\n- Add support for `application/json` and `text/plain` encodings for `useSubmit`/`fetcher.submit`. To reflect these additional types, `useNavigation`/`useFetcher` now also contain `navigation.json`/`navigation.text` and `fetcher.json`/`fetcher.text` which include the json/text submission if applicable. ([#10413](https://github.com/remix-run/react-router/pull/10413))\n\n### Patch Changes\n\n- When submitting a form from a `submitter` element, prefer the built-in `new FormData(form, submitter)` instead of the previous manual approach in modern browsers (those that support the new `submitter` parameter) ([#9865](https://github.com/remix-run/react-router/pull/9865))\n - For browsers that don't support it, we continue to just append the submit button's entry to the end, and we also add rudimentary support for `type=\"image\"` buttons\n - If developers want full spec-compliant support for legacy browsers, they can use the `formdata-submitter-polyfill`\n- Call `window.history.pushState/replaceState` _before_ updating React Router state (instead of after) so that `window.location` matches `useLocation` during synchronous React 17 rendering ([#10448](https://github.com/remix-run/react-router/pull/10448))\n - โš ๏ธ Note: generally apps should not be relying on `window.location` and should always reference `useLocation` when possible, as `window.location` will not be in sync 100% of the time (due to `popstate` events, concurrent mode, etc.)\n- Avoid calling `shouldRevalidate` for fetchers that have not yet completed a data load ([#10623](https://github.com/remix-run/react-router/pull/10623))\n- Strip `basename` from the `location` provided to `` to match the `useLocation` behavior ([#10550](https://github.com/remix-run/react-router/pull/10550))\n- Strip `basename` from locations provided to `unstable_useBlocker` functions to match the `useLocation` behavior ([#10573](https://github.com/remix-run/react-router/pull/10573))\n- Fix `unstable_useBlocker` key issues in `StrictMode` ([#10573](https://github.com/remix-run/react-router/pull/10573))\n- Fix `generatePath` when passed a numeric `0` value parameter ([#10612](https://github.com/remix-run/react-router/pull/10612))\n- Fix `tsc --skipLibCheck:false` issues on React 17 ([#10622](https://github.com/remix-run/react-router/pull/10622))\n- Upgrade `typescript` to 5.1 ([#10581](https://github.com/remix-run/react-router/pull/10581))\n\n**Full Changelog**: [`v6.13.0...v6.14.0`](https://github.com/remix-run/react-router/compare/react-router@6.13.0...react-router@6.14.0)\n\n## v6.13.0\n\nDate: 2023-06-14\n\n### What's Changed\n\n`6.13.0` is really a patch release in spirit but comes with a SemVer minor bump since we added a new future flag.\n\n#### `future.v7_startTransition`\n\nThe **tl;dr;** is that `6.13.0` is the same as [`6.12.0`](https://github.com/remix-run/react-router/releases/tag/react-router%406.12.0) bue we've moved the usage of `React.startTransition` behind an opt-in `future.v7_startTransition` [future flag](https://reactrouter.com/v6/guides/api-development-strategy) because we found that there are applications in the wild that are currently using `Suspense` in ways that are incompatible with `React.startTransition`.\n\nTherefore, in `6.13.0` the default behavior will no longer leverage `React.startTransition`:\n\n```jsx\n\n {/*...*/}\n\n\n\n```\n\nIf you wish to enable `React.startTransition`, pass the future flag to your router component:\n\n```jsx\n\n {/*...*/}\n\n\n\n```\n\nWe recommend folks adopt this flag sooner rather than later to be better compatible with React concurrent mode, but if you run into issues you can continue without the use of `React.startTransition` until v7. Issues usually boil down to creating net-new promises during the render cycle, so if you run into issues when opting into `React.startTransition`, you should either lift your promise creation out of the render cycle or put it behind a `useMemo`.\n\n### Minor Changes\n\n- Move `React.startTransition` usage behinds a future flag ([#10596](https://github.com/remix-run/react-router/pull/10596))\n\n### Patch Changes\n\n- Work around webpack/terser `React.startTransition` minification bug in production mode ([#10588](https://github.com/remix-run/react-router/pull/10588))\n\n**Full Changelog**: [`v6.12.1...v6.13.0`](https://github.com/remix-run/react-router/compare/react-router@6.12.1...react-router@6.13.0)\n\n## v6.12.1\n\nDate: 2023-06-08\n\n> [!WARNING]\n> Please use version `6.13.0` or later instead of `6.12.0`/`6.12.1`. These versions suffered from some Webpack build/minification issues resulting failed builds or invalid minified code in your production bundles. See [#10569](https://github.com/remix-run/react-router/pull/10569) and [#10579](https://github.com/remix-run/react-router/issues/10579) for more details.\n\n### Patch Changes\n\n- Adjust feature detection of `React.startTransition` to fix webpack + react 17 compilation error ([#10569](https://github.com/remix-run/react-router/pull/10569))\n\n**Full Changelog**: [`v6.12.0...v6.12.1`](https://github.com/remix-run/react-router/compare/react-router@6.12.0...react-router@6.12.1)\n\n## v6.12.0\n\nDate: 2023-06-06\n\n> [!WARNING]\n> Please use version `6.13.0` or later instead of `6.12.0`/`6.12.1`. These versions suffered from some Webpack build/minification issues resulting failed builds or invalid minified code in your production bundles. See [#10569](https://github.com/remix-run/react-router/pull/10569) and [#10579](https://github.com/remix-run/react-router/issues/10579) for more details.\n\n### What's Changed\n\n#### `React.startTransition` support\n\nWith `6.12.0` we've added better support for suspending components by wrapping the internal router state updates in [`React.startTransition`](https://react.dev/reference/react/startTransition). This means that, for example, if one of your components in a destination route suspends and you have not provided a [`Suspense`](https://react.dev/reference/react/Suspense) boundary to show a fallback, React will delay the rendering of the new UI and show the old UI until that asynchronous operation resolves. This could be useful for waiting for things such as waiting for images or CSS files to load (and technically, yes, you could use it for data loading but we'd still recommend using loaders for that ๐Ÿ˜€). For a quick overview of this usage, check out [Ryan's demo on Twitter](https://twitter.com/remix_run/status/1658976420767604736).\n\n### Minor Changes\n\n- Wrap internal router state updates with `React.startTransition` ([#10438](https://github.com/remix-run/react-router/pull/10438))\n\n### Patch Changes\n\n- Allow fetcher revalidations to complete if submitting fetcher is deleted ([#10535](https://github.com/remix-run/react-router/pull/10535))\n- Re-throw `DOMException` (`DataCloneError`) when attempting to perform a `PUSH` navigation with non-serializable state. ([#10427](https://github.com/remix-run/react-router/pull/10427))\n- Ensure revalidations happen when hash is present ([#10516](https://github.com/remix-run/react-router/pull/10516))\n- Upgrade `jest` and `jsdom` ([#10453](https://github.com/remix-run/react-router/pull/10453))\n- Updated dependencies:\n - `@remix-run/router@1.6.3` ([Changelog](https://github.com/remix-run/react-router/blob/main/packages/router/CHANGELOG.md#163))\n\n**Full Changelog**: [`v6.11.2...v6.12.0`](https://github.com/remix-run/react-router/compare/react-router@6.11.2...react-router@6.12.0)\n\n## v6.11.2\n\nDate: 2023-05-17\n\n### Patch Changes\n\n- Fix `basename` duplication in descendant `` inside a `` ([#10492](https://github.com/remix-run/react-router/pull/10492))\n- Fix bug where initial data load would not kick off when hash is present ([#10493](https://github.com/remix-run/react-router/pull/10493))\n- Export `SetURLSearchParams` type ([#10444](https://github.com/remix-run/react-router/pull/10444))\n- Fix Remix HMR-driven error boundaries by properly reconstructing new routes and `manifest` in `_internalSetRoutes` ([#10437](https://github.com/remix-run/react-router/pull/10437))\n\n**Full Changelog**: [`v6.11.1...v6.11.2`](https://github.com/remix-run/react-router/compare/react-router@6.11.1...react-router@6.11.2)\n\n## v6.11.1\n\nDate: 2023-05-03\n\n### Patch Changes\n\n- Fix usage of `Component` API within descendant `` ([#10434](https://github.com/remix-run/react-router/pull/10434))\n- Fix bug when calling `useNavigate` from `` inside a `` ([#10432](https://github.com/remix-run/react-router/pull/10432))\n- Fix usage of `` in strict mode when using a data router ([#10435](https://github.com/remix-run/react-router/pull/10435))\n- Fix `basename` handling when navigating without a path ([#10433](https://github.com/remix-run/react-router/pull/10433))\n- \"Same hash\" navigations no longer re-run loaders to match browser behavior (i.e. `/path#hash -> /path#hash`) ([#10408](https://github.com/remix-run/react-router/pull/10408))\n\n**Full Changelog**: [`v6.11.0...v6.11.1`](https://github.com/remix-run/react-router/compare/react-router@6.11.0...react-router@6.11.1)\n\n## v6.11.0\n\nDate: 2023-04-28\n\n### Minor Changes\n\n- Enable `basename` support in `useFetcher` ([#10336](https://github.com/remix-run/react-router/pull/10336))\n - If you were previously working around this issue by manually prepending the `basename` then you will need to remove the manually prepended `basename` from your `fetcher` calls (`fetcher.load('/basename/route') -> fetcher.load('/route')`)\n- Updated dependencies:\n - `@remix-run/router@1.6.0` ([Changelog](https://github.com/remix-run/react-router/blob/main/packages/router/CHANGELOG.md#160))\n\n### Patch Changes\n\n- When using a `RouterProvider`, `useNavigate`/`useSubmit`/`fetcher.submit` are now stable across location changes, since we can handle relative routing via the `@remix-run/router` instance and get rid of our dependence on `useLocation()` ([#10336](https://github.com/remix-run/react-router/pull/10336))\n - When using `BrowserRouter`, these hooks remain unstable across location changes because they still rely on `useLocation()`\n- Fetchers should no longer revalidate on search params changes or routing to the same URL, and will only revalidate on `action` submissions or `router.revalidate` calls ([#10344](https://github.com/remix-run/react-router/pull/10344))\n- Fix inadvertent re-renders when using `Component` instead of `element` on a route definition ([#10287](https://github.com/remix-run/react-router/pull/10287))\n- Fail gracefully on `` and other invalid URL values ([#10367](https://github.com/remix-run/react-router/pull/10367))\n- Switched from `useSyncExternalStore` to `useState` for internal `@remix-run/router` router state syncing in ``. We found some [subtle bugs](https://codesandbox.io/s/use-sync-external-store-loop-9g7b81) where router state updates got propagated _before_ other normal `useState` updates, which could lead to foot guns in `useEffect` calls. ([#10377](https://github.com/remix-run/react-router/pull/10377), [#10409](https://github.com/remix-run/react-router/pull/10409))\n- Log loader/action errors caught by the default error boundary to the console in dev for easier stack trace evaluation ([#10286](https://github.com/remix-run/react-router/pull/10286))\n- Fix bug preventing rendering of descendant `` when `RouterProvider` errors existed ([#10374](https://github.com/remix-run/react-router/pull/10374))\n- Fix detection of `useNavigate` in the render cycle by setting the `activeRef` in a layout effect, allowing the `navigate` function to be passed to child components and called in a `useEffect` there ([#10394](https://github.com/remix-run/react-router/pull/10394))\n- Allow `useRevalidator()` to resolve a loader-driven error boundary scenario ([#10369](https://github.com/remix-run/react-router/pull/10369))\n- Enhance `LoaderFunction`/`ActionFunction` return type to prevent `undefined` from being a valid return value ([#10267](https://github.com/remix-run/react-router/pull/10267))\n- Ensure proper 404 error on `fetcher.load` call to a route without a `loader` ([#10345](https://github.com/remix-run/react-router/pull/10345))\n- Decouple `AbortController` usage between revalidating fetchers and the thing that triggered them such that the unmount/deletion of a revalidating fetcher doesn't impact the ongoing triggering navigation/revalidation ([#10271](https://github.com/remix-run/react-router/pull/10271))\n\n**Full Changelog**: [`v6.10.0...v6.11.0`](https://github.com/remix-run/react-router/compare/react-router@6.10.0...react-router@6.11.0)\n\n## v6.10.0\n\nDate: 2023-03-29\n\n### What's Changed\n\nWe recently published a post over on the Remix Blog titled [\"Future Proofing Your Remix App\"](https://remix.run/blog/future-flags) that goes through our strategy to ensure smooth upgrades for your Remix and React Router apps going forward. React Router `6.10.0` adds support for these flags (for data routers) which you can specify when you create your router:\n\n```js\nconst router = createBrowserRouter(routes, {\n future: {\n // specify future flags here\n },\n});\n```\n\nYou can also check out the docs [here](https://reactrouter.com/en/dev/guides/api-development-strategy) and [here](https://reactrouter.com/en/dev/routers/create-browser-router#future).\n\n### Minor Changes\n\n#### `future.v7_normalizeFormMethod`\n\nThe first future flag being introduced is `future.v7_normalizeFormMethod` which will normalize the exposed `useNavigation()/useFetcher()` `formMethod` fields as uppercase HTTP methods to align with the `fetch()` (and some Remix) behavior. ([#10207](https://github.com/remix-run/react-router/pull/10207))\n\n- When `future.v7_normalizeFormMethod` is unspecified or set to `false` (default v6 behavior),\n - `useNavigation().formMethod` is lowercase\n - `useFetcher().formMethod` is lowercase\n- When `future.v7_normalizeFormMethod === true`:\n - `useNavigation().formMethod` is UPPERCASE\n - `useFetcher().formMethod` is UPPERCASE\n\n### Patch Changes\n\n- Fix `createStaticHandler` to also check for `ErrorBoundary` on routes in addition to `errorElement` ([#10190](https://github.com/remix-run/react-router/pull/10190))\n- Fix route ID generation when using Fragments in `createRoutesFromElements` ([#10193](https://github.com/remix-run/react-router/pull/10193))\n- Provide fetcher submission to `shouldRevalidate` if the fetcher action redirects ([#10208](https://github.com/remix-run/react-router/pull/10208))\n- Properly handle `lazy()` errors during router initialization ([#10201](https://github.com/remix-run/react-router/pull/10201))\n- Remove `instanceof` check for `DeferredData` to be resilient to ESM/CJS boundaries in SSR bundling scenarios ([#10247](https://github.com/remix-run/react-router/pull/10247))\n- Update to latest `@remix-run/web-fetch@4.3.3` ([#10216](https://github.com/remix-run/react-router/pull/10216))\n\n**Full Changelog**: [`v6.9.0...v6.10.0`](https://github.com/remix-run/react-router/compare/react-router@6.9.0...react-router@6.10.0)\n\n## v6.9.0\n\nDate: 2023-03-10\n\n### What's Changed\n\n#### `Component`/`ErrorBoundary` route properties\n\nReact Router now supports an alternative way to define your route `element` and `errorElement` fields as React Components instead of React Elements. You can instead pass a React Component to the new `Component` and `ErrorBoundary` fields if you choose. There is no functional difference between the two, so use whichever approach you prefer ๐Ÿ˜€. You shouldn't be defining both, but if you do `Component`/`ErrorBoundary` will \"win\"\n\n**Example JSON Syntax**\n\n```jsx\n// Both of these work the same:\nconst elementRoutes = [{\n path: '/',\n element: ,\n errorElement: ,\n}]\n\nconst componentRoutes = [{\n path: '/',\n Component: Home,\n ErrorBoundary: HomeError,\n}]\n\nfunction Home() { ... }\nfunction HomeError() { ... }\n```\n\n**Example JSX Syntax**\n\n```jsx\n// Both of these work the same:\nconst elementRoutes = createRoutesFromElements(\n } errorElement={ } />\n);\n\nconst componentRoutes = createRoutesFromElements(\n \n);\n\nfunction Home() { ... }\nfunction HomeError() { ... }\n```\n\n#### Introducing Lazy Route Modules\n\nIn order to keep your application bundles small and support code-splitting of your routes, we've introduced a new `lazy()` route property. This is an async function that resolves the non-route-matching portions of your route definition (`loader`, `action`, `element`/`Component`, `errorElement`/`ErrorBoundary`, `shouldRevalidate`, `handle`).\n\nLazy routes are resolved on initial load and during the `loading` or `submitting` phase of a navigation or fetcher call. You cannot lazily define route-matching properties (`path`, `index`, `children`) since we only execute your lazy route functions after we've matched known routes.\n\nYour `lazy` functions will typically return the result of a dynamic import.\n\n```jsx\n// In this example, we assume most folks land on the homepage so we include that\n// in our critical-path bundle, but then we lazily load modules for /a and /b so\n// they don't load until the user navigates to those routes\nlet routes = createRoutesFromElements(\n }>\n } />\n import(\"./a\")} />\n import(\"./b\")} />\n ,\n);\n```\n\nThen in your lazy route modules, export the properties you want defined for the route:\n\n```jsx\nexport async function loader({ request }) {\n let data = await fetchData(request);\n return json(data);\n}\n\n// Export a `Component` directly instead of needing to create a React Element from it\nexport function Component() {\n let data = useLoaderData();\n\n return (\n <>\n

You made it!

\n

{data}

\n \n );\n}\n\n// Export an `ErrorBoundary` directly instead of needing to create a React Element from it\nexport function ErrorBoundary() {\n let error = useRouteError();\n return isRouteErrorResponse(error) ? (\n

\n {error.status} {error.statusText}\n

\n ) : (\n

{error.message || error}

\n );\n}\n```\n\nAn example of this in action can be found in the [`examples/lazy-loading-router-provider`](https://github.com/remix-run/react-router/tree/main/examples/lazy-loading-router-provider) directory of the repository. For more info, check out the [`lazy` docs](https://reactrouter.com/v6/route/lazy).\n\n๐Ÿ™Œ Huge thanks to @rossipedia for the [Initial Proposal](https://github.com/remix-run/react-router/discussions/9826) and [POC Implementation](https://github.com/remix-run/react-router/pull/9830).\n\n### Minor Changes\n\n- Add support for `route.Component`/`route.ErrorBoundary` properties ([#10045](https://github.com/remix-run/react-router/pull/10045))\n- Add support for `route.lazy` ([#10045](https://github.com/remix-run/react-router/pull/10045))\n\n### Patch Changes\n\n- Improve memoization for context providers to avoid unnecessary re-renders ([#9983](https://github.com/remix-run/react-router/pull/9983))\n- Fix `generatePath` incorrectly applying parameters in some cases ([#10078](https://github.com/remix-run/react-router/pull/10078))\n- `[react-router-dom-v5-compat]` Add missed data router API re-exports ([#10171](https://github.com/remix-run/react-router/pull/10171))\n\n**Full Changelog**: [`v6.8.2...v6.9.0`](https://github.com/remix-run/react-router/compare/react-router@6.8.2...react-router@6.9.0)\n\n## v6.8.2\n\nDate: 2023-02-27\n\n### Patch Changes\n\n- Treat same-origin absolute URLs in `` as external if they are outside of the router `basename` ([#10135](https://github.com/remix-run/react-router/pull/10135))\n- Correctly perform a hard redirect for same-origin absolute URLs outside of the router `basename` ([#10076](https://github.com/remix-run/react-router/pull/10076))\n- Fix SSR of absolute `` urls ([#10112](https://github.com/remix-run/react-router/pull/10112))\n- Properly escape HTML characters in `StaticRouterProvider` serialized hydration data ([#10068](https://github.com/remix-run/react-router/pull/10068))\n- Fix `useBlocker` to return `IDLE_BLOCKER` during SSR ([#10046](https://github.com/remix-run/react-router/pull/10046))\n- Ensure status code and headers are maintained for `defer` loader responses in `createStaticHandler`'s `query()` method ([#10077](https://github.com/remix-run/react-router/pull/10077))\n- Change `invariant` to an `UNSAFE_invariant` export since it's only intended for internal use ([#10066](https://github.com/remix-run/react-router/pull/10066))\n\n**Full Changelog**: [`v6.8.1...v6.8.2`](https://github.com/remix-run/react-router/compare/react-router@6.8.1...react-router@6.8.2)\n\n## v6.8.1\n\nDate: 2023-02-06\n\n### Patch Changes\n\n- Remove inaccurate console warning for POP navigations and update active blocker logic ([#10030](https://github.com/remix-run/react-router/pull/10030))\n- Only check for differing origin on absolute URL redirects ([#10033](https://github.com/remix-run/react-router/pull/10033))\n- Improved absolute url detection in `Link` component (now also supports `mailto:` urls) ([#9994](https://github.com/remix-run/react-router/pull/9994))\n- Fix partial object (search or hash only) pathnames losing current path value ([#10029](https://github.com/remix-run/react-router/pull/10029))\n\n**Full Changelog**: [`v6.8.0...v6.8.1`](https://github.com/remix-run/react-router/compare/react-router@6.8.0...react-router@6.8.1)\n\n## v6.8.0\n\nDate: 2023-01-26\n\n### Minor Changes\n\nSupport absolute URLs in ``. If the URL is for the current origin, it will still do a client-side navigation. If the URL is for a different origin then it will do a fresh document request for the new origin. ([#9900](https://github.com/remix-run/react-router/pull/9900))\n\n```tsx\n {/* Document request */}\n {/* Document request */}\n {/* Client-side navigation */}\n```\n\n### Patch Changes\n\n- Fixes 2 separate issues for revalidating fetcher `shouldRevalidate` calls ([#9948](https://github.com/remix-run/react-router/pull/9948))\n - The `shouldRevalidate` function was only being called for _explicit_ revalidation scenarios (after a mutation, manual `useRevalidator` call, or an `X-Remix-Revalidate` header used for cookie setting in Remix). It was not properly being called on _implicit_ revalidation scenarios that also apply to navigation `loader` revalidation, such as a change in search params or clicking a link for the page we're already on. It's now correctly called in those additional scenarios.\n - The parameters being passed were incorrect and inconsistent with one another since the `current*`/`next*` parameters reflected the static `fetcher.load` URL (and thus were identical). Instead, they should have reflected the navigation that triggered the revalidation (as the `form*` parameters did). These parameters now correctly reflect the triggering navigation.\n- Fix bug with search params removal via `useSearchParams` ([#9969](https://github.com/remix-run/react-router/pull/9969))\n- Respect `preventScrollReset` on `` ([#9963](https://github.com/remix-run/react-router/pull/9963))\n- Fix navigation for hash routers on manual URL changes ([#9980](https://github.com/remix-run/react-router/pull/9980))\n- Use `pagehide` instead of `beforeunload` for ``. This has better cross-browser support, specifically on Mobile Safari. ([#9945](https://github.com/remix-run/react-router/pull/9945))\n- Do not short circuit on hash change only mutation submissions ([#9944](https://github.com/remix-run/react-router/pull/9944))\n- Remove `instanceof` check from `isRouteErrorResponse` to avoid bundling issues on the server ([#9930](https://github.com/remix-run/react-router/pull/9930))\n- Detect when a `defer` call only contains critical data and remove the `AbortController` ([#9965](https://github.com/remix-run/react-router/pull/9965))\n- Send the name as the value when url-encoding `File` `FormData` entries ([#9867](https://github.com/remix-run/react-router/pull/9867))\n- `react-router-dom-v5-compat` - Fix SSR `useLayoutEffect` `console.error` when using `CompatRouter` ([#9820](https://github.com/remix-run/react-router/pull/9820))\n\n**Full Changelog**: [`v6.7.0...v6.8.0`](https://github.com/remix-run/react-router/compare/react-router@6.7.0...react-router@6.8.0)\n\n## v6.7.0\n\nDate: 2023-01-18\n\n### Minor Changes\n\n- Add `unstable_useBlocker`/`unstable_usePrompt` hooks for blocking navigations within the app's location origin ([#9709](https://github.com/remix-run/react-router/pull/9709), [#9932](https://github.com/remix-run/react-router/pull/9932))\n- Add `preventScrollReset` prop to `` ([#9886](https://github.com/remix-run/react-router/pull/9886))\n\n### Patch Changes\n\n- Added pass-through event listener options argument to `useBeforeUnload` ([#9709](https://github.com/remix-run/react-router/pull/9709))\n- Fix `generatePath` when optional params are present ([#9764](https://github.com/remix-run/react-router/pull/9764))\n- Update `` to accept `ReactNode` as children function return result ([#9896](https://github.com/remix-run/react-router/pull/9896))\n- Improved absolute redirect url detection in actions/loaders ([#9829](https://github.com/remix-run/react-router/pull/9829))\n- Fix URL creation with memory histories ([#9814](https://github.com/remix-run/react-router/pull/9814))\n- Fix scroll reset if a submission redirects ([#9886](https://github.com/remix-run/react-router/pull/9886))\n- Fix 404 bug with same-origin absolute redirects ([#9913](https://github.com/remix-run/react-router/pull/9913))\n- Streamline `jsdom` bug workaround in tests ([#9824](https://github.com/remix-run/react-router/pull/9824))\n\n**Full Changelog**: [`v6.6.2...v6.7.0`](https://github.com/remix-run/react-router/compare/react-router@6.6.2...react-router@6.7.0)\n\n## v6.6.2\n\nDate: 2023-01-09\n\n### Patch Changes\n\n- Ensure `useId` consistency during SSR ([#9805](https://github.com/remix-run/react-router/pull/9805))\n\n**Full Changelog**: [`v6.6.1...v6.6.2`](https://github.com/remix-run/react-router/compare/react-router@6.6.1...react-router@6.6.2)\n\n## v6.6.1\n\nDate: 2022-12-23\n\n### Patch Changes\n\n- Include submission info in `shouldRevalidate` on action redirects ([#9777](https://github.com/remix-run/react-router/pull/9777), [#9782](https://github.com/remix-run/react-router/pull/9782))\n- Reset `actionData` on action redirect to current location ([#9772](https://github.com/remix-run/react-router/pull/9772))\n\n**Full Changelog**: [`v6.6.0...v6.6.1`](https://github.com/remix-run/react-router/compare/react-router@6.6.0...react-router@6.6.1)\n\n## v6.6.0\n\nDate: 2022-12-21\n\n### What's Changed\n\nThis minor release is primarily to stabilize our SSR APIs for Data Routers now that we've wired up the new `RouterProvider` in Remix as part of the [React Router-ing Remix](https://remix.run/blog/react-routering-remix) work.\n\n### Minor Changes\n\n- Remove `unstable_` prefix from `createStaticHandler`/`createStaticRouter`/`StaticRouterProvider` ([#9738](https://github.com/remix-run/react-router/pull/9738))\n- Add `useBeforeUnload()` hook ([#9664](https://github.com/remix-run/react-router/pull/9664))\n\n### Patch Changes\n\n- Support uppercase `` and `useSubmit` method values ([#9664](https://github.com/remix-run/react-router/pull/9664))\n- Fix `\n\n {blocker.state === \"blocked\" ? (\n
\n

You have unsaved changes!

\n \n \n

\n ) : blocker.state === \"proceeding\" ? (\n

Navigating away with unsaved changes...

\n ) : null}\n \n );\n}\n```\n\nThe `blocker` received by the user would be either `unblocked`, `blocked`, or `proceeding`:\n\n- `unblocked` is the normal idle state\n- `blocked` means the user tried to navigate and the blocker function returned `true` and the navigation was blocked. When in a `blocked` state the blocker would expose `proceed`/`reset` functions:\n - `blocker.proceed()` would allow the blocked navigation to happen (and thus lose unsaved changes). This proceed navigation would _not_ re-run the blocker function.\n - `blocker.reset()` would reset the blocker back to `unblocked` and remain on the current page\n- `proceeding` indicates the navigation from `blocker.proceed()` is in-progress - and essentially reflects the non-`idle` `navigation.state` during that navigation\n\nOther navigations and/or interruptions to proceeding navigations would reset the blocker back to an unblocked state.\n\n~We will not provide a `usePrompt` implementation, however it would be somewhat trivial to implement that on top of `useBlocker` in userland.~\n\nWe decided in the end to include a `usePrompt` even though it's got more broken edge cases than `useBlocker`:\n\n- It's only a handful of lines of code\n- It's more similar to what we had in v5\n- We don't know for sure how many folks were using this in v5, since the github commenters are not a complete sample\n- It has a lower barrier to implement than a custom modal UI\n- We plan to document that it breaks in more cases, in weird ways, and even differently across browsers.\n\n### Blocker State Diagram\n\n```mermaid\ngraph TD;\n Unblocked -->|navigate| A{shouldBlock?};\n A -->|false| Unblocked;\n A -->|true| Blocked;\n Blocked -->|blocker.proceed| Proceeding;\n Blocked -->|Unblocked Navigation| Unblocked;\n Blocked -->|blocker.reset| Unblocked;\n Proceeding -->|Navigation Complete| Unblocked;\n Proceeding -->|Navigation Interrupted| Unblocked;\n```\n\n### Open Questions\n\n- Initial implementation is for data-router usage (6.4+). We still need to back-port to 6.3 and earlier to help folks migrate from `v5 -> v6 BrowserRouter -> v6 RouterProvider`\n - We decided that this can just be net-new 6.4+ API. A v5 app should be able to migrate to a 6.4+ `RouterProvider` just as easily as a 6.3 `BrowserRouter`\n- We should probably pass the `historyAction`/`location` of the active navigation to `shouldBlock()` similar to how v5 did it. Should we also pass the submission (`formMethod`, `formData`, etc.)?\n - For now we landed on calling the blocker function with `{ currentLocation, nextLocation, historyAction }` to align naming loosely with `shouldRevalidate`. Can always extend that API ion the future if needed (with form submission info).\n- I think since we are not providing `usePrompt`, we should accept a `beforeUnload:boolean` option to add cross-navigation handling in an opt-in fashion.\n - `beforeUnload` is also unreliable because it does not prevent the user from doing additional back/forward navigations ao this is not included out of the box and can be implemented in user-land.\n" }, { "path": "decisions/0001-use-npm-to-manage-npm-dependencies-for-deno-projects.md", "content": "# Use `npm` to manage NPM dependencies for Deno projects\n\nDate: 2022-05-10\n\nStatus: accepted\n\n## Context\n\nDeno has three ways to manage dependencies:\n\n1. Inlined URL imports: `import {...} from \"https://deno.land/x/blah\"`\n2. [deps.ts](https://deno.land/manual/examples/manage_dependencies)\n3. [Import maps](https://deno.land/manual/linking_to_external_code/import_maps)\n\nAdditionally, NPM packages can be accessed as Deno modules via [Deno-friendly CDNs](https://deno.land/manual/node/cdns#deno-friendly-cdns) like https://esm.sh.\n\nRemix has some requirements around dependencies:\n\n- Remix treeshakes dependencies that are free of side-effects.\n- Remix sets the environment (dev/prod/test) across all code, including dependencies, at runtime via the `NODE_ENV` environment variable.\n- Remix depends on some NPM packages that should be specified as peer dependencies (notably, `react` and `react-dom`).\n\n### Treeshaking\n\nTo optimize bundle size, Remix [treeshakes](https://esbuild.github.io/api/#tree-shaking) your app's code and dependencies.\nThis also helps to separate browser code and server code.\n\nUnder the hood, the Remix compiler uses [esbuild](https://esbuild.github.io).\nLike other bundlers, `esbuild` uses [`sideEffects` in `package.json` to determine when it is safe to eliminate unused imports](https://esbuild.github.io/api/#conditionally-injecting-a-file).\n\nUnfortunately, URL imports do not have a standard mechanism for marking packages as side-effect free.\n\n### Setting dev/prod/test environment\n\nDeno-friendly CDNs set the environment via a query parameter (e.g. `?dev`), not via an environment variable.\nThat means changing environment requires changing the URL import in the source code.\nWhile you could use multiple import maps (`dev.json`, `prod.json`, etc...) to workaround this, import maps have other limitations:\n\n- standard tooling for managing import maps is not available\n- import maps are not composeable, so any dependencies that use import maps must be manually accounted for\n\n### Specifying peer dependencies\n\nEven if import maps were perfected, CDNs compile each dependency in isolation.\nThat means that specifying peer dependencies becomes tedious and error-prone as the user needs to:\n\n- determine which dependencies themselves depend on `react` (or other similar peer dependency), even if indirectly.\n- manually figure out which `react` version works across _all_ of these dependencies\n- set that version for `react` as a query parameter in _all_ of the URLs for the identified dependencies\n\nIf any dependencies change (added, removed, version change),\nthe user must repeat all of these steps again.\n\n## Decision\n\n### Use `npm` to manage NPM dependencies for Deno\n\nDo not use Deno-friendly CDNs for NPM dependencies in Remix projects using Deno.\n\nUse `npm` and `node_modules/` to manage NPM dependencies like `react` for Remix projects, even when using Deno with Remix.\n\nDeno module dependencies (e.g. from `https://deno.land`) can still be managed via URL imports.\n\n### Allow URL imports\n\nRemix will preserve any URL imports in the built bundles as external dependencies,\nletting your browser runtime and server runtime handle them accordingly.\nThat means that you may:\n\n- use URL imports for the browser\n- use URL imports for the server, if your server runtime supports it\n\nFor example, Node will throw errors for URL imports, while Deno will resolve URL imports as normal.\n\n### Do not support import maps\n\nRemix will not yet support import maps.\n\n## Consequences\n\n- URL imports will not be treeshaken.\n- Users can specify environment via the `NODE_ENV` environment variable at runtime.\n- Users won't have to do error-prone, manual dependency resolution.\n\n### VS Code type hints\n\nUsers may configure an import map for the [Deno extension for VS Code](denoland.vscode-deno) to enable type hints for NPM-managed dependencies within their Deno editor:\n\n`.vscode/resolve_npm_imports_in_deno.json`\n\n```json\n{\n \"// This import map is used solely for the denoland.vscode-deno extension.\": \"\",\n \"// Remix does not support import maps.\": \"\",\n \"// Dependency management is done through `npm` and `node_modules/` instead.\": \"\",\n \"// Deno-only dependencies may be imported via URL imports (without using import maps).\": \"\",\n\n \"imports\": {\n \"react\": \"https://esm.sh/react@18.0.0\",\n \"react-dom\": \"https://esm.sh/react-dom@18.0.0\",\n \"react-dom/server\": \"https://esm.sh/react-dom@18.0.0/server\"\n }\n}\n```\n\n`.vscode/settings.json`\n\n```json\n{\n \"deno.enable\": true,\n \"deno.importMap\": \"./.vscode/resolve_npm_imports_in_deno.json\"\n}\n```\n" }, { "path": "decisions/0002-do-not-clone-request.md", "content": "# Do not clone request\n\nDate: 2022-05-13\n\nStatus: accepted\n\n## Context\n\nTo allow multiple loaders / actions to read the body of a request, we have been cloning the request before forwarding it to user-code. This is not the best thing to do as some runtimes will begin buffering the body to allow for multiple consumers. It also goes against \"the platform\" that states a request body should only be consumed once.\n\n## Decision\n\nDo not clone requests before they are passed to user-code (actions, handleDocumentRequest, handleDataRequest), and remove body from request passed to loaders. Loaders should be thought of as a \"GET\" / \"HEAD\" request handler. These request methods are not allowed to have a body, therefore you should not be reading it in your Remix loader function.\n\n## Consequences\n\nLoaders always receive a null body for the request.\n\nIf you are reading the request body in both an action and handleDocumentRequest or handleDataRequest this will now fail as the body will have already been read. If you wish to continue reading the request body in multiple places for a single request against recommendations, consider using `.clone()` before reading it; just know this comes with tradeoffs.\n" }, { "path": "decisions/0002-lazy-route-modules.md", "content": "# Lazy Route Modules\n\nDate: 2023-02-21\n\nStatus: accepted\n\n## Context\n\nIn a data-aware React Router application (``), the router needs to be aware of the route tree ahead of time so it can match routes and execute loaders/actions _prior_ to rendering the destination route. This is different than in non-data-aware React Router applications (``) where you could nest `` sub-tree anywhere in your application, and compose together `` and `React.lazy()` to dynamically load \"new\" portions of your routing tree as the user navigated through the application. The downside of this approach in `BrowserRouter` is that it's a render-then-fetch cycle which produces network waterfalls and nested spinners, two things that we're aiming to eliminate in `RouterProvider` applications.\n\nThere were ways to [manually code-split][manually-code-split] in a `RouterProvider` application but they can be a bit verbose and tedious to do manually. As a result of this DX, we received a [Remix Route Modules Proposal][proposal] from the community along with a [POC implementation][poc] (thanks `@rossipedia` ๐Ÿ™Œ).\n\n## Original POC\n\nThe original POC idea was to implement this in user-land where `element`/`errorElement` would be transformed into `React.lazy()` calls and `loader`/`action` would load the module and then execute the `loader`/`action`:\n\n```js\n// Assuming route.module is a function returning a Remix-style route module\nlet Component = React.lazy(route.module);\nroute.element = ;\nroute.loader = async (args) => {\n const { loader } = await route.module();\n return typeof loader === \"function\" ? loader(args) : null;\n};\n```\n\nThis approach got us pretty far but suffered from some limitations being done in user-land since it did not have access to some router internals to make for a more seamless integration. Namely, it _had_ to put every possible property onto a route since it couldn't know ahead of time whether the route module would resolve with the matching property. For example, will `import('./route')` return an `errorElement`? Who knows!\n\nTo combat this, a `route.use` property was considered which would allow the user to define the exports of the module:\n\n```js\nconst route = {\n path: \"/\",\n module: () => import(\"./route\"),\n use: [\"loader\", \"element\"],\n};\n```\n\nThis wasn't ideal since it introduced a tight coupling of the file contents and the route definitions.\n\nFurthermore, since the goal of `RouterProvider` is to reduce spinners, it felt incorrect to automatically introduce `React.lazy` and thus expect Suspense boundaries for elements that we expected to be fully fetched _prior_ to rendering the destination route.\n\n## Decision\n\nGiven what we learned from the original POC, we felt we could do this a bit leaner with an implementation inside the router. Data router apps already have an asynchronous pre-render flow where we could hook in and run this logic. A few advantages of doing this inside of the router include:\n\n- We can load at a more specific spot internal to the router\n- We can access the navigation `AbortSignal` in case the `lazy()` call gets interrupted\n- We can also load once and update the internal route definition so subsequent navigations don't have a repeated `lazy()` call\n- We don't have issue with knowing whether or not an `errorElement` exists since we will have updated the route prior to updating any UI state\n\nThis proved to work out quite well as we did our own POC so we went with this approach in the end. Now, any time we enter a `submitting`/`loading` state we first check for a `route.lazy` definition and resolve that promise first and update the internal route definition with the result.\n\nThe resulting API looks like this, assuming you want to load your homepage in the main bundle, but lazily load the code for the `/about` route. Note we're using the new `Component` API introduced along with this work.\n\n```jsx\n// app.jsx\nconst router = createBrowserRouter([\n {\n path: \"/\",\n Component: Layout,\n children: [\n {\n index: true,\n Component: Home,\n },\n {\n path: \"about\",\n lazy: () => import(\"./about\"),\n },\n ],\n },\n]);\n```\n\nAnd then your `about.jsx` file would export the properties to be lazily defined on the route:\n\n```jsx\n// about.jsx\nexport function loader() { ... }\n\nexport function Component() { ... }\n```\n\n## Choices\n\nHere's a few choices we made along the way:\n\n### Immutable Route Properties\n\nA route has 3 types of fields defined on it:\n\n- Path matching properties: `path`, `index`, `caseSensitive` and `children`\n - While not strictly used for matching, `id` is also considered static since it is needed up-front to uniquely identify all defined routes\n- Data loading properties: `loader`, `action`, `hasErrorBoundary`, `shouldRevalidate`\n- Rendering properties: `handle` and the framework-aware `element`/`errorElement`/`Component`/`ErrorBoundary`\n\nThe `route.lazy()` method is focused on lazy-loading the data loading and rendering properties, but cannot update the path matching properties because we have to path match _first_ before we can even identify which matched routes include a `lazy()` function. Therefore, we do not allow path matching route keys to be updated by `lazy()`, and will log a warning if you return one of those properties from your lazy() method.\n\n## Static Route Properties\n\nSimilar to how you cannot override any immutable path-matching properties, you also cannot override any statically defined data-loading or rendering properties (and will log the a console warning if you attempt to). This allows you to statically define aspects that you don't need (or wish) to lazy load. Two potential use-cases her might be:\n\n1. Using a small statically-defined `loader`/`action` which just hits an API endpoint to load/submit data.\n - In fact this is an interesting option we've optimized React Router to detect this and call any statically defined loader/action handlers in parallel with `lazy` (since `lazy` will be unable to update the `loader`/`action` anyway!). This will provide the ability to obtain the most-optimal parallelization of loading your component in parallel with your data fetches.\n2. Re-using a common statically-defined `ErrorBoundary` across multiple routes\n\n### Addition of route `Component` and `ErrorBoundary` fields\n\nIn React Router v6, routes define `element` properties because it allows static prop passing as well as fitting nicely in the JSX render-tree-defined route trees:\n\n```jsx\n\n \n } />\n \n\n```\n\nHowever, in a React Router 6.4+ landscape when using `RouterProvider`, routes are defined statically up-front to enable data-loading, so using element feels arguably a bit awkward outside of a JSX tree:\n\n```js\nconst routes = [\n {\n path: \"/\",\n element: ,\n },\n];\n```\n\nIt also means that you cannot easily use hooks inline, and have to add a level of indirection to access hooks.\n\nThis gets a bit more awkward with the introduction of `lazy()` since your file now has to export a root-level JSX element:\n\n```jsx\n// home.jsx\nexport const element = \n\nfunction Homepage() { ... }\n```\n\nIn reality, what we want in this \"static route definition\" landscape is just the component for the Route:\n\n```js\nconst routes = [\n {\n path: \"/\",\n Component: Homepage,\n },\n];\n```\n\nThis has a number of advantages in that we can now use inline component functions to access hooks, provide props, etc. And we also simplify the exports of a `lazy()` route module:\n\n```jsx\nconst routes = [\n {\n path: \"/\",\n // You can include just the component\n Component: Homepage,\n },\n {\n path: \"/a\",\n // Or you can inline your component and pass props\n Component: () => ,\n },\n {\n path: \"/b\",\n // And even use use hooks without indirection ๐Ÿ’ฅ\n Component: () => {\n let data = useLoaderData();\n return ;\n },\n },\n];\n```\n\nSo in the end, the work for `lazy()` introduced support for `route.Component` and `route.ErrorBoundary`, which can be statically or lazily defined. They will take precedence over `element`/`errorElement` if both happen to be defined, but for now both are acceptable ways to define routes. We think we'll be expanding the `Component` API in the future for stronger type-safety since we can pass it inferred-type `loaderData` etc. so in the future that _may_ become the preferred API.\n\n### Interruptions\n\nPreviously when a link was clicked or a form was submitted, since we had the `action`/`loader` defined statically up-front, they were immediately executed and there was no chance for an interruption _before calling the handler_. Now that we've introduced the concept of `lazy()` there is a period of time prior to executing the handler where the user could interrupt the navigation by clicking to a new location. In order to keep behavior consistent with lazily-loaded routes and statically defined routes, if a `lazy()` function is interrupted React Router _will still call the returned handler_. As always, the user can leverage `request.signal.aborted` inside the handler to short-circuit on interruption if desired.\n\nThis is important because `lazy()` is only ever run once in an application session. Once lazy has completed it updates the route in place, and all subsequent navigations to that route use the now-statically-defined properties. Without this behavior, routes would behave differently on the _first_ navigation versus _subsequent_ navigations which could introduce subtle and hard-to-track-down bugs.\n\nAdditionally, since `lazy()` functions are intended to return a static definition of route `loader`/`element`/etc. - if multiple navigations happen to the same route in parallel, the first `lazy()` call to resolve will \"win\" and update the route, and the returned values from any other `lazy()` executions will be ignored. This should not be much of an issue in practice though as modern bundlers latch onto the same promise for repeated calls to `import()` so in those cases the first call will still \"win\".\n\n### Error Handling\n\nIf an error is thrown by `lazy()` we catch that in the same logic as if the error was thrown by the `action`/`loader` and bubble it to the nearest `errorElement`.\n\n## Consequences\n\nNot so much as a consequence, but more of limitation - we still require the routing tree up-front for the most efficient data-loading. This means that we can't _yet_ support quite the same nested `` use-cases as before (particularly with respect to microfrontends), but we have ideas for how to solve that as an extension of this concept in the future.\n\nAnother slightly edge-case concept we discovered is that in DIY SSR applications using `createStaticHandler` and `StaticRouterProvider`, it's possible to server-render a lazy route and send up its hydration data. But then we may _not_ have those routes loaded in our client-side hydration:\n\n```jsx\nconst routes = [{\n path: '/',\n lazy: () => import(\"./route\"),\n}]\nlet router = createBrowserRouter(routes, {\n hydrationData: window.__hydrationData,\n});\n\n// โš ๏ธ At this point, the router has the data but not the route definition!\n\nReactDOM.hydrateRoot(\n document.getElementById(\"app\")!,\n \n);\n```\n\nIn the above example, we've server-rendered our `/` route and therefore we _don't_ want to render a `fallbackElement` since we already have the SSR'd content, and the router doesn't need to \"initialize\" because we've provided the data in `hydrationData`. However, if we're hydrating into a route that includes `lazy`, then we _do_ need to initialize that lazy route.\n\nThe real solution for this is to do what Remix does and know your matched routes and preload their modules ahead of time and hydrate with synchronous route definitions. This is a non-trivial process through so it's not expected that every DIY SSR use-case will handle it. Instead, the router will not be initialized until any initially matched lazy routes are loaded, and therefore we need to delay the hydration or our `RouterProvider`.\n\nThe recommended way to do this is to manually match routes against the initial location and load/update any lazy routes before creating your router:\n\n```jsx\n// Determine if any of the initial routes are lazy\nlet lazyMatches = matchRoutes(routes, window.location)?.filter(\n (m) => m.route.lazy\n);\n\n// Load the lazy matches and update the routes before creating your router\n// so we can hydrate the SSR-rendered content synchronously\nif (lazyMatches && lazyMatches.length > 0) {\n await Promise.all(\n lazyMatches.map(async (m) => {\n let routeModule = await m.route.lazy!();\n Object.assign(m.route, { ...routeModule, lazy: undefined });\n })\n );\n}\n\n// Create router and hydrate\nlet router = createBrowserRouter(routes)\nReactDOM.hydrateRoot(\n document.getElementById(\"app\")!,\n \n);\n```\n\n[manually-code-split]: https://www.infoxicator.com/en/react-router-6-4-code-splitting\n[proposal]: https://github.com/remix-run/react-router/discussions/9826\n[poc]: https://github.com/remix-run/react-router/pull/9830\n" }, { "path": "decisions/0003-data-strategy.md", "content": "# Data Strategy\n\nDate: 2024-01-31\n\nStatus: accepted\n\n## Context\n\nIn order to implement \"Single Fetch\" in Remix ([Issue][single-fetch-issue], [RFC][single-fetch-rfc]), we need to expose some level of control over the internal data fetching behaviors of the `@remix-run/router`. This way, while React Router will run loaders in parallel by default, Remix can opt-into making a single fetch call to the server for all loaders.\n\n## Decisions\n\n### `dataStrategy`\n\nTo achieve the above, we propose to add an optional `dataStrategy` config which can be passed in by the application. The idea is that `dataStrategy` will accept an array of `matches` to load and will return a parallel array of results for those matches.\n\n```js\nfunction dataStrategy(arg: DataStrategyFunctionArgs): DataResult[];\n\ninterface DataStrategyFunctionArgs\n extends DataFunctionArgs {\n matches: AgnosticDataStrategyMatch[];\n}\n\ninterface DataFunctionArgs {\n request: Request;\n params: Params;\n context?: Context;\n}\n```\n\nThere's a [comment][responsibilities-comment] here from Jacob which does a good job of outlining the current responsibilities, but basically React Router in it's current state handles 4 aspects when it comes to executing loaders for a given URL - `dataStrategy` is largely intended to handle step 3:\n\n1. Match routes for URL\n2. Determine what routes to load (via `shouldRevalidate`)\n3. Call `loader` functions in parallel\n4. Decode Responses\n\n### Inputs\n\nThe primary input is `matches`, since the user needs to know what routes match and eed to have loaders executed. We also wanted to provide a way for the user to call the \"default\" internal behavior so they could easily change from parallel to sequential without having to re-invent the wheel and manually call loaders, decode responses, etc. The first idea for this API was to pass a `defaultStrategy(match)` parameter so they could call that per-match:\n\n```js\nfunction dataStrategy({ matches }) {\n // Call in parallel\n return Promise.all(matches.map(m => defaultStrategy((m))));\n\n // Call sequentially\n let results = []\n for (let match of matches) {\n results.push(await defaultStrategy(match))\n }\n return results;\n}\n```\n\nโš ๏ธ `defaultStrategy` was eliminated in favor of `match.resolve`.\n\nWe also originally intended to expose a `type: 'loader' | 'action`' field as a way to presumably let them call `match.route.loader`/`match.route.action` directly - but we have since decided against that with the `match.resolve` API.\n\nโš ๏ธ `type` was eliminated in favor of `match.resolve`.\n\n`dataStrategy` is control _when_ handlers are called, not _how_. RR is in charge of calling them with the right parameters.\n\n### Outputs\n\nOriginally, we planned on making the `DataResult` API public, which is a union of the different types of results (`SuccessResult`, `ErrorResult`, `RedirectResult`, `DeferResult`). However, as we kept evolving and did some internal refactoring to separate calling loaders from decoding results - we realized that all we really need is a simpler `HandlerResult`:\n\n```ts\ninterface HandlerResult {\n type: ResultType.success | ResultType.error;\n result: any;\n}\n```\n\nIf the user returns us one of those per-match, we can internally convert it to a `DataResult`.\n\n- If `result` is a `Response` then we can handle unwrapping the data and processing any redirects (may produce a `SuccessResult`, `ErrorResult`, or `RedirectResult`)\n- If `result` is a `DeferredData` instance, convert to `DeferResult`\n- If result is anything else we don't touch the data, it's either a `SuccessResult` or `ErrorResult` based on `type`\n - This is important because it's lets the end user opt into a different decoding strategy of their choice. If they return us a Response, we decode it. If not, we don't touch it.\n\n### Decoding Responses\n\nInitially, we intended for `dataStrategy` to handle (3), and considered an optional `decodeResponse` API for (4) - but we decided that the decoding of responses was a small enough undertaking using standard Fetch APIs (i.e., `res.json`) that it didn't warrant a custom property - and they could just call those APIs directly. The `defaultStrategy` parameter would handle performing 3 the normal way that RR would.\n\nโš ๏ธ `decodeResponse` is made obsolete by `HandlerResult`\n\n### Handling `route.lazy`\n\nThere's a nuanced step we missed in our sequential steps above. If a route was\nusing `route.lazy`, we may need to load the route before we can execute the `loader`. There's two options here:\n\n1. We pre-execute all `route.lazy` methods before calling `dataStrategy`\n2. We let `dataStrategy` execute them accordingly\n\n(1) has a pretty glaring perf issue in that it blocks _any_ loaders from running until _all_ `route.lazy`'s have resolved. So if route A is super small but has a slow loader, and route B is large but has a fast loader:\n\n```\n|-- route a lazy --> |-- route a loader --------------->|\n|-- route b lazy ------------------------>|-- route b loader --> |\n```\n\nThis is no bueno. Instead, we want option (2) where the users can run these sequentially per-route - and \"loading the route\" is just part of the \"loading the data\" step\n\n```\n|-- route a lazy -->|-- route a loader ---------------> |\n|-- route b lazy ------------------------>|-- route b loader -->|\n```\n\nTherefore, we're introducing the concept of a `DataStrategyMatch` which is just like a `RouteMatch` but the `match.route` field is a `Promise`. We'll kick off the executions of route.lazy and then you can wait for them to complete prior to calling the loader:\n\n```js\nfunction dataStrategy({ matches, defaultStrategy }) {\n return Promise.all(\n matches.map((m) => match.route.then((route) => route.loader(/* ... */))),\n );\n}\n```\n\nThere are also statically defined properties that live outside of lazy, so those are extended right onto `match.route`. This allows you to define loaders statically and run them in parallel with `route.lazy`:\n\n```js\nfunction dataStrategy({ matches, defaultStrategy }) {\n // matches[0].route => Promise\n // matches[0].route.id => string\n // matches[0].route.index => boolean\n // matches[0].route.path => string\n}\n```\n\nโš ๏ธ This match.route as a function API was removed in favor of `match.resolve`\n\n### Handling `shouldRevalidate` behavior\n\nWe considered how to handle `shouldRevalidate` behavior. There's sort of 2 basic approaches:\n\n1. We pre-filter and only hand the user `matchesToLoad`\n2. We hand the user all matches and let them filter\n - This would probably also require a new `defaultShouldRevalidate(match) => boolean` parameter passed to `dataStrategy`\n\nI _think_ (1) is preferred to keep the API at a minimum and avoid leaking into _other_ ways to opt-out of revalidation. We already have an API for that so let's lean into it.\n\nAdditionally, another big con of (2) is that if we want to let them make revalidation decisions inside `dataStrategy` - we need to expose all of the information required for that (`currentUrl`, `currentParams`, `nextUrl`, `nextParams`, `submission` info, `actionResult`, etc.) - the API becomes a mess.\n\nTherefore we are aiming to stick with one and let `shouldRevalidate` be the only way to opt-out of revalidation.\n\n### Handling actions and fetchers\n\nThus far, we've been mostly concerned with how to handle navigational loaders where they are multiple matched routes and loaders to run. But what about actions and fetchers where we only run a handler for a single leaf match? The quick answer to this is to just send a single-length array with the match in question:\n\n```js\n// loaders\nlet matchesToLoad = getMatchesToLoad(request, matches);\nlet results = await dataStrategy({\n request,\n params,\n matches: matchesToLoad,\n type: \"loader\",\n defaultStrategy,\n});\n\n// action\nlet actionMatch = getTargetMatch(request, matches);\nlet actionResults = await dataStrategy({\n request,\n params,\n matches: [actionMatch],\n type: \"action\",\n defaultStrategy,\n});\nlet actionResult = actionResults[0];\n\n// fetcher loader/action\nlet fetcherMatch = getTargetMatch(request, matches);\nlet fetcherResults = await dataStrategy({\n request,\n params,\n matches: [fetcherMatch],\n type: \"loader\", // or \"action\"\n defaultStrategy,\n});\nlet fetcherResult = fetcherResults[0];\n```\n\nThis way, the user's implementation can just always operate on the `matches` array and it'll work for all use cases.\n\n```js\n// Sample strategy to run sequentially\nasync function dataStrategy({ request, params, matches, type }) {\n let results = [];\n for (let match of matches) {\n let result = await match.route[type]({ request, params });\n result.push(result);\n }\n return results;\n}\n```\n\n### What about middlewares?\n\nAs we thought more and more about this API, it became clear that the concept of \"process data for a route\" (step 3 above) was not necessarily limited to the `loader`/`action` and that there are data-related APIs on the horizon such as `middleware` and `context` that would also fall under the `dataStrategy` umbrella! In fact, a well-implemented `dataStrategy` could alleviate the need for first-class APIs - even if only initially. Early adopters could use `dataStrategy` to implement their own middlewares and we could see which patterns rise to the top and adopt them as first class `route.middleware` or whatever.\n\nSo how would middleware work? The general idea is that middleware runs sequentially top-down prior to the loaders running. And if you bring `context` into the equation - they also run top down and middlewares/loaders/actions receive the context from their level and above in the tree - but they do not \"see\" any context from below them in the tree.\n\nA user-land implementation turns out not to be too bad assuming routes define `middleware`/`context` on `handle`:\n\n```js\n// Assume routes look like this:\nlet route = {\n id: \"parent\",\n path: \"/parent\",\n loader: () => {},\n handle: {\n // context can provide multiple keyed contexts\n context: {\n parent: () => ({ id: \"parent\" }),\n },\n // middleware receives context as an argument\n middleware(context) {\n context.parent.whatever = \"PARENT MIDDLEWARE\";\n },\n },\n};\n\nasync function dataStrategy({ request, params, matches, type }) {\n // Run context/middleware sequentially\n let contexts = {};\n for (let match of matches) {\n if (m.route.handle?.context) {\n for (let [id, ctx] of Object.entries(m.route.handle.context)) {\n contexts[key] = ctx();\n }\n }\n if (m.route.handle?.middleware) {\n m.route.handle.middleware(context);\n }\n }\n\n // Run loaders in parallel (or run the solo action)\n return Promise.all(\n matches.map(async (m, i) => {\n // Only expose contexts from this level and above\n let context = matches.slice(0, i + 1).reduce((acc, m) => {\n Object.keys(m.route.handle?.context).forEach((k) => {\n acc[k] = contexts[k];\n });\n return acc;\n }, {});\n try {\n return {\n type: ResultType.data,\n data: await m.route[type]?.({ request, params, context });,\n };\n } catch (error) {\n return {\n type: ResultType.error,\n error,\n };\n }\n })\n );\n}\n```\n\nโŒ Nope - this doesn't actually work!\n\nRemember above where we decided to _pre-filter_ the matches based on `shouldRevalidate`? That breaks any concept of middleware since even if we don't intend to load a route, we need to run middleware on all parents before the loader. So we _must_ expose at least the `matches` at or above that level in the tree - and more likely _all_ matches to `dataStrategy` if it's to be able to implement middleware.\n\nAnd then, once we expose _multiple_ matches - we need to tell the user if they're supposed to actually run the handlers on those matches or only on a leaf/target match.\n\nI think there's a few options here:\n\n**Option 1 - `routeMatches` and `handlerMatches`**\n\nWe could add a second array of the \"full\" set of matches for the route and then middleware would operate on that set, and handlers would operate on the filtered set (renamed to `handlerMatches`) here. This still preserves the pre-filtering and keeps `shouldRevalidate` logic out of `dataStrategy`.\n\n```js\nasync function dataStrategy({ request, params, routeMatches, handlerMatches, type }) {\n // Run context/middleware sequentially\n let contexts = {};\n for (let match of routeMatches) { ... }\n\n // Run loaders in parallel\n return Promise.all(\n handlerMatches.map(async (m, i) => { ... })\n );\n}\n```\n\n**Option 2 - new field on `DataStrategyMatch`**\n\nSince we're already introducing a concept of a `DataStrategyMatch` to handle `route.lazy`, we could lean into that and expose something on those matches that indicate if they need to have their handler run or not?\n\n```js\n// Inside React Router, assume navigate from /a/ -> /b and we don't need to\n// re-run the root loader\nlet dataStrategyMatches = [{\n route: { id: 'root', loader() {}, ... }\n runHandler: false // determined via shouldRevalidate\n}, {\n route: { id: 'b', loader() {}, ... }\n runHandler: true // determined via shouldRevalidate\n}]\n```\n\nThen, the user could use this to differentiate between middlewares and handlers:\n\n```js\nasync function dataStrategy({ request, params, matches, type }) {\n // Run context/middleware sequentially\n let contexts = {};\n for (let match of matches) { ... }\n\n // Run loaders in parallel\n let matchesToLoad = matches.filter(m => m.runHandler);\n return Promise.all(\n matchesToLoad.map(async (m, i) => { ... })\n );\n}\n```\n\n**Option 3 - new function on `DataStrategyMatch`**\n\nExtending on the idea above - it all started to feel super leaky and full of implementation-details. Why are users manually filtering? Or manually passing parameters to loaders/actions? Using a `type` field to know which to call? Waiting on a `match.route` Promise before calling the loader?\n\nThat's wayyyy to many rough edges for us to document and users to get wrong (rightfully so!).\n\nWhy can't we just do it all? Let's wrap _all_ of that up into a single `match.resolve()` function that:\n\n- Waits for `route.lazy` to resolve (if needed)\n- No-ops if the route isn't supposed to revalidate\n - Open question here if we return the _current_ data from these no-ops or return `undefined`?\n - We decided _not_ to expose this data for now since we don't have a good use case\n- Knows whether to call the `loader` or the `action`\n- Allows users to pass _additional_ params to loaders/actions for middleware/context use cases.\n\n```js\n// Simplest case - call all loaders in parallel just like current behavior\nfunction dataStrategy({ matches }) {\n // No more type, defaultStrategy, or match.route promise APIs!\n return Promise.all(matches.map(match => {\n // resolve `route.lazy` if needed and call loader/action\n return m.resolve();\n });\n}\n\n// More advanced case - call loader sequentially passing a context through\nasync function dataStrategy({ matches }) {\n let ctx = {};\n let results = [];\n for (let match of matches) {\n // You can pass a \"handlerOverride\" function to resolve giving you control\n // over how/if to call the handler. The argument passed to `handler` will\n // be passed as the second argument to your `loader`/`action`:\n // function loader({ request }, ctx) {...}\n let result = await m.resolve((handler) => {\n return handler(ctx);\n });\n results.push(result);\n });\n return results;\n}\n\n// More performant case leveraging a middleware type abstraction which lets loaders\n// still run in parallel after sequential middlewares:\nfunction dataStrategy({ matches }) {\n // Can implement middleware as above since you now get all matches\n let context = runMiddlewares(matches);\n\n // Call all loaders in parallel (no params to pass) but you _can_ pass you\n // own argument to `resolve` and it will come in as `loader({ request }, handlerArg)`\n // So you can send middleware context through to loaders/actions\n return Promise.all(matches.map(match => {\n return m.resolve(context);\n });\n\n // Note we don't do any filtering above - if a match doesn't need to load,\n // `match.resolve` is no-op. Just like `serverLoader` is a no-op in `clientLoader`\n // when it doesn't need to run\n}\n\n// Advanced case - single-fetch type approach\n// More advanced case - call loader sequentially passing a context through\nasync function dataStrategy({ matches }) {\n let singleFetchData = await makeSingleFetchCall()\n // Assume we get back:\n // { data: { [routeId]: unknown }, errors: { [routeId]: unknown } }\n let results = [];\n for (let match of matches) {\n // Don't even call the handler since we have the data we need from single fetch\n let result = await m.resolve(() => {\n if (singleFetchData.errors?.[m.route.id]) {\n return {\n type: 'error',\n result: singleFetchData.errors?.[m.route.id]\n }\n }\n return {\n type: 'data',\n result: singleFetchData.data?.[m.route.id]\n }\n });\n results.push(result);\n });\n return results;\n}\n```\n\n## Status codes\n\nInitially, we thought we could just let the `handlerOverride`return or throw and then internally we could convert the returned/thrown valuer into a `HandlerResult`. However, this didn't work for the `unstable_skipActionRevalidation` behavior we wanted to implement with Single Fetch.\n\nIf users returned normal Response's it would be fine, since we could decode the response internally and also know the status. However, if user's wanted to do custom response decoding (i.e., use `turbo-stream` like we did in single fetch) then there was no way to return/throw data _and the status code from the response_ without introducing something like the `ErrorResponse` API which holds a status and data. We decided to make `HandlerResult` public API and put an optional `status` field on it.\n\nThis means that if you just call resolve with no `handlerOverride` you never need to know about `HandlerResult`. If you do pass a `handlerOverride`, then you need to return a proper HandlerResult with `type:\"data\"|\"error\"`.\n\n[single-fetch-issue]: https://github.com/remix-run/remix/issues/7641\n[single-fetch-rfc]: https://github.com/remix-run/remix/discussions/7640\n[responsibilities-comment]: https://github.com/remix-run/remix/issues/7641#issuecomment-1836635069\n" }, { "path": "decisions/0003-infer-types-for-useloaderdata-and-useactiondata-from-loader-and-action-via-generics.md", "content": "# Infer types for `useLoaderData` and `useActionData` from `loader` and `action` via generics\n\nDate: 2022-07-11\n\nStatus: Superseded by [#0012](./0012-type-inference.md)\n\n## Context\n\nGoal: End-to-end type safety for `useLoaderData` and `useActionData` with great Developer Experience (DX)\n\nRelated discussions:\n\n- [remix-run/remix#1254](https://github.com/remix-run/remix/pull/1254)\n- [remix-run/remix#3276](https://github.com/remix-run/remix/pull/3276)\n\n---\n\nIn Remix v1.6.4, types for both `useLoaderData` and `useActionData` are parameterized with a generic:\n\n```tsx\ntype MyLoaderData = {\n /* ... */\n};\ntype MyActionData = {\n /* ... */\n};\n\nexport default function Route() {\n const loaderData = useLoaderData();\n const actionData = useActionData();\n return
{/* ... */}
;\n}\n```\n\nFor end-to-end type safety, it is then the user's responsibility to make sure that `loader` and `action` also use the same type in the `json` generic:\n\n```ts\nexport const loader: LoaderFunction = () => {\n return json({\n /* ... */\n });\n};\n\nexport const action: ActionFunction = () => {\n return json({\n /* ... */\n });\n};\n```\n\n### Diving into `useLoaderData`'s and `useActionData`'s generics\n\nTracing through the `@remix-run/react` source code (v1.6.4), you'll find that `useLoaderData` returns an `any` type that is implicitly type cast to whatever type gets passed into the `useLoaderData` generic:\n\n```ts\n// https://github.com/remix-run/remix/blob/v1.6.4/packages/remix-react/components.tsx#L1370\nexport function useLoaderData(): T {\n return useRemixRouteContext().data; //\n}\n\n// https://github.com/remix-run/remix/blob/v1.6.4/packages/remix-react/components.tsx#L73\nfunction useRemixRouteContext(): RemixRouteContextType {\n /* ... */\n}\n\n// https://github.com/remix-run/remix/blob/v1.6.4/packages/remix-react/components.tsx#L56\ninterface RemixRouteContextType {\n data: AppData;\n id: string;\n}\n\n// https://github.com/remix-run/remix/blob/v1.6.4/packages/remix-react/data.ts#L4\nexport type AppData = any;\n```\n\nBoiling this down, the code looks like:\n\n```ts\nlet data: any;\n\n// somewhere else, `loader` gets called an sets `data` to some value\n\nfunction useLoaderData(): T {\n return data; // <-- Typescript casts this `any` to `T`\n}\n```\n\n`useLoaderData` isn't basing its return type on how `data` was set (i.e. the return value of `loader`) nor is it validating the data.\nIt's just blindly casting `data` to whatever the user passed in for the generic `T`.\n\n### Issues with current approach\n\nThe developer experience is subpar.\nUsers are required to write redundant code for the data types that could have been inferred from the arguments to `json`.\nChanges to the data shape require changing _both_ the declared `type` or `interface` as well as the argument to `json`.\n\nAdditionally, the current approach encourages users to pass the same type to `json` with the `loader` and to `useLoaderData`, but **this is a footgun**!\n`json` can accept data types like `Date` that are JSON serializable, but `useLoaderData` will return the _serialized_ type:\n\n```ts\ntype MyLoaderData = {\n birthday: Date;\n};\n\nexport const loader: LoaderFunction = () => {\n return json({ birthday: new Date(\"February 15, 1992\") });\n};\n\nexport default function Route() {\n const { birthday } = useLoaderData();\n // ^ `useLoaderData` tricks Typescript into thinking this is a `Date`, when in fact it's a `string`!\n}\n```\n\nAgain, the same goes for `useActionData`.\n\n### Solution criteria\n\n- Return type of `useLoaderData` and `useActionData` should somehow be inferred from `loader` and `action`, not blindly type cast\n- Return type of `loader` and `action` should be inferred\n - Necessarily, return type of `json` should be inferred from its input\n- No module side-effects (so higher-order functions like `makeLoader` is definitely a no).\n- `json` should allow everything that `JSON.stringify` allows.\n- `json` should allow only what `JSON.stringify` allows.\n- `useLoaderData` should not return anything that `JSON.parse` can't return.\n\n### Key insight: `loader` and `action` are an _implicit_ inputs\n\nWhile there's been interest in inferring the types for `useLoaderData` based on `loader`, there was [hesitance to use a Typescript generic to do so](https://github.com/remix-run/remix/pull/3276#issuecomment-1164764821).\nTypescript generics are apt for specifying or inferring types for _inputs_, not for blindly type casting output types.\n\nA key factor in the decision was identifying that `loader` and `action` are _implicit_ inputs of `useLoaderData` and `useActionData`.\n\nIn other words, if `loader` and `useLoaderData` were guaranteed to run in the same process (and not cross the network), then we could write `useLoaderData(loader)`, specifying `loader` as an explicit input for `useLoaderData`.\n\n```ts\n// _conceptually_ `loader` is an input for `useLoaderData`\nfunction useLoaderData(loader: Loader) {\n /*...*/\n}\n```\n\nThough `loader` and `useLoaderData` exist together in the same file at development-time, `loader` does not exist at runtime in the browser.\nWithout the `loader` argument to infer types from, `useLoaderData` needs a way to learn about `loader`'s type at compile-time.\n\nAdditionally, `loader` and `useLoaderData` are both managed by Remix across the network.\nWhile it's true that Remix doesn't \"own\" the network in the strictest sense, having `useLoaderData` return data that does not correspond to its `loader` is an exceedingly rare edge-case.\n\nSame goes for `useActionData`.\n\n---\n\nA similar case is how [Prisma](https://www.prisma.io/) infers types from database schemas available at runtime, even though there are (exceedingly rare) edge-cases where that database schema _could_ be mutated after compile-time but before run-time.\n\n## Decision\n\nExplicitly provide type of the implicit `loader` input for `useLoaderData` and then infer the return type for `useLoaderData`.\nDo the same for `action` and `useActionData`.\n\n```ts\nexport const loader = async (args: LoaderArgs) => {\n // ...\n return json(/*...*/);\n};\n\nexport default function Route() {\n const data = useLoaderData();\n // ...\n}\n```\n\nAdditionally, the inferred return type for `useLoaderData` will only include serializable (JSON) types.\n\n### Return `unknown` when generic is omitted\n\nOmitting the generic for `useLoaderData` or `useActionData` results in `any` being returned.\nThis hides potential type errors from the user.\nInstead, we'll change the return type to `unknown`.\n\n```ts\ntype MyLoaderData = {\n /*...*/\n};\n\nexport default function Route() {\n const data = useLoaderData();\n // ^? unknown\n}\n```\n\nNote: Since this would be a breaking change, changing the return type to `unknown` will be slated for v2.\n\n### Deprecate non-inferred types via generics\n\nPassing in a non-inferred type for `useLoaderData` is hiding an unsafe type cast.\nUsing the `useLoaderData` in this way will be deprecated in favor of an explicit type cast that clearly communicates the assumptions being made:\n\n```ts\ntype MyLoaderData = {\n /*...*/\n};\n\nexport default function Route() {\n const dataGeneric = useLoaderData(); // <-- will be deprecated\n const dataCast = useLoaderData() as MyLoaderData; // <- use this instead\n}\n```\n\n## Consequences\n\n- Users can continue to provide non-inferred types by type casting the result of `useLoaderData` or `useActionData`\n- Users can opt-in to inferred types by using `typeof loader` or `typeof action` at the generic for `useLoaderData` or `useActionData`.\n- Return types for `loader` and `action` will be the sources-of-truth for the types inferred for `useLoaderData` and `useActionData`.\n- Users do not need to write redundant code to align types across the network\n- Return type of `useLoaderData` and `useActionData` will correspond to the JSON _serialized_ types from `json` calls in `loader` and `action`, eliminating a class of errors.\n- `LoaderFunction` and `ActionFunction` should not be used when opting into type inference as they override the inferred return types.[^1]\n\n๐Ÿšจ Users who opt-in to inferred types **MUST** return a `TypedResponse` from `json` and **MUST NOT** return a bare object:\n\n```ts\nconst loader = () => {\n // NO\n return { hello: \"world\" };\n\n // YES\n return json({ hello: \"world\" });\n};\n```\n\n[^1]: The proposed `satisfies` operator for Typescript would let `LoaderFunction` and `ActionFunction` enforce function types while preserving the narrower inferred return type: https://github.com/microsoft/TypeScript/issues/47920\n" }, { "path": "decisions/0004-streaming-apis.md", "content": "---\ntitle: Remix (and React Router) Streaming APIs\n---\n\n# Title\n\nDate: 2022-07-27\n\nStatus: accepted\n\n## Context\n\nRemix aims to provide first-class support for React 18's streaming capabilities. Throughout the development process we went through many iterations and naming schemes around the APIs we plan to build into Remix to support streaming, so this document aims to lay out the final names we chose and the reasons behind it.\n\nIt's also worth nothing that even in a single-page-application without SSR-streaming, the same concepts still apply so these decisions were made with React Router 6.4.0 in mind as well - which will support the same Data APIs from Remix.\n\n## Decision\n\nStreaming in Remix can be thought of as having 3 touch points with corresponding APIs:\n\n1. _Initiating_ a streamed response in your `loader` can be done by returning a `defer(object)` call from your `loader` in which some of the keys on `object` are `Promise` instances\n2. _Accessing_ a streamed response from `useLoaderData`\n 1. No new APIs here - when you return a `defer()` response from your loader, you'll get `Promise` values inside your `useLoaderData` object ๐Ÿ‘Œ\n3. _Rendering_ a streamed value (with fallback and error handling) in your component\n 1. You can render a `Promise` from `useLoaderData()` with the `` component\n 2. `` accepts an `errorElement` prop to handle error UI\n 3. `` should be wrapped with a `` component to handle your loading UI\n\n## Details\n\nIn the spirit of `#useThePlatform` we've chosen to leverage the `Promise` API to represent these \"eventually available\" values. When Remix receives a `defer()` response back from a `loader`, it needs to serialize that `Promise` over the network to the client application (prompting Jacob to coin the phrase [_\"promise teleportation over the network\"_][promise teleportation] ๐Ÿ”ฅ).\n\n### Initiating\n\nIn order to initiate a streamed response in your `loader`, you can use the `defer()` utility which accepts a JSON object with `Promise` values from your `loader`.\n\n```tsx\nexport async function loader() {\n return defer({\n // Await this, don't stream\n critical: await fetchCriticalData(),\n // Don't await this - stream it!\n lazy: fetchLazyData(),\n });\n}\n```\n\nBy not using `await` on `fetchLazyData()` Remix knows that this value is not ready yet _but eventually will be_ and therefore Remix will leverage a streamed HTTP response allowing it to send up the resolved/rejected value when available. Essentially serializing/teleporting that Promise over the network via a streamed HTTP response.\n\nJust like `json()`, the `defer()` will accept a second optional `responseInit` param that lets you customize the resulting `Response` (i.e., in case you need to set custom headers).\n\nThe name `defer` was settled on as a corollary to `\n```\n\n---\n\n[$link]: https://www.youtube.com/watch?v=dQw4w9WgXcQ\n[createbrowserrouter]: ./routers/create-browser-router\n" }, { "path": "docs/explanation/README", "content": "Explanations:\n\n- Theoretical Knowledge\n- Understanding Oriented\n- Useful when we're studying\n" }, { "path": "docs/explanation/backend-for-frontend.md", "content": "---\ntitle: Backend For Frontend\n---\n\n# Backend For Frontend\n\n[MODES: framework]\n\n
\n
\n\nWhile React Router can serve as your fullstack application, it also fits perfectly into the \"Backend for Frontend\" architecture.\n\nThe BFF strategy employs a web server with a job scoped to serving the frontend web app and connecting it to the services it needs: your database, mailer, job queues, existing backend APIs (REST, GraphQL), etc. Instead of your UI integrating directly from the browser to these services, it connects to the BFF, and the BFF connects to your services.\n\nMature apps already have a lot of backend application code in Ruby, Elixir, PHP, etc., and there's no reason to justify migrating it all to a server-side JavaScript runtime just to get the benefits of React Router. Instead, you can use your React Router app as a backend for your frontend.\n\nYou can use `fetch` right from your loaders and actions to your backend.\n\n```tsx lines=[7,13,17]\nimport escapeHtml from \"escape-html\";\n\nexport async function loader() {\n const apiUrl = \"https://api.example.com/some-data.json\";\n const res = await fetch(apiUrl, {\n headers: {\n Authorization: `Bearer ${process.env.API_TOKEN}`,\n },\n });\n\n const data = await res.json();\n\n const prunedData = data.map((record) => {\n return {\n id: record.id,\n title: record.title,\n formattedBody: escapeHtml(record.content),\n };\n });\n return { prunedData };\n}\n```\n\nThere are several benefits of this approach vs. fetching directly from the browser. The highlighted lines above show how you can:\n\n1. Simplify third-party integrations and keep tokens and secrets out of client bundles\n2. Prune the data down to send less kB over the network, speeding up your app significantly\n3. Move a lot of code from browser bundles to the server, like `escapeHtml`, which speeds up your app. Additionally, moving code to the server usually makes your code easier to maintain since server-side code doesn't have to worry about UI states for async operations\n\nAgain, React Router can be used as your only server by talking directly to the database and other services with server-side JavaScript APIs, but it also works perfectly as a backend for your frontend. Go ahead and keep your existing API server for application logic and let React Router connect the UI to it.\n" }, { "path": "docs/explanation/code-splitting.md", "content": "---\ntitle: Automatic Code Splitting\n---\n\n# Automatic Code Splitting\n\n[MODES: framework]\n\n
\n
\n\nWhen using React Router's framework features, your application is automatically code split to improve the performance of initial load times when users visit your application.\n\n## Code Splitting by Route\n\nConsider this simple route config:\n\n```tsx filename=app/routes.ts\nimport {\n type RouteConfig,\n route,\n} from \"@react-router/dev/routes\";\n\nexport default [\n route(\"/contact\", \"./contact.tsx\"),\n route(\"/about\", \"./about.tsx\"),\n] satisfies RouteConfig;\n```\n\nInstead of bundling all routes into a single giant build, the modules referenced (`contact.tsx` and `about.tsx`) become entry points to the bundler.\n\nBecause these entry points are coupled to URL segments, React Router knows just from a URL which bundles are needed in the browser, and more importantly, which are not.\n\nIf the user visits `\"/about\"` then the bundles for `about.tsx` will be loaded but not `contact.tsx`. This drastically reduces the JavaScript footprint for initial page loads and speeds up your application.\n\n## Removal of Server Code\n\nAny server-only [Route Module APIs][route-module] will be removed from the bundles. Consider this route module:\n\n```tsx\nexport async function loader() {\n return { message: \"hello\" };\n}\n\nexport async function action() {\n console.log(Date.now());\n return { ok: true };\n}\n\nexport async function headers() {\n return { \"Cache-Control\": \"max-age=300\" };\n}\n\nexport default function Component({ loaderData }) {\n return
{loaderData.message}
;\n}\n```\n\nAfter building for the browser, only the `Component` will still be in the bundle, so you can use server-only code in the other module exports.\n\n[route-module]: ../../start/framework/route-module\n" }, { "path": "docs/explanation/concurrency.md", "content": "---\ntitle: Network Concurrency Management\n---\n\n# Network Concurrency Management\n\n[MODES: framework, data]\n\n
\n
\n\nWhen building web applications, managing network requests can be a daunting task. The challenges of ensuring up-to-date data and handling simultaneous requests often lead to complex logic in the application to deal with interruptions and race conditions. React Router simplifies this process by automating network management while mirroring and expanding upon the intuitive behavior of web browsers.\n\nTo help understand how React Router handles concurrency, it's important to remember that after `form` submissions, React Router will fetch fresh data from the `loader`s. This is called revalidation.\n\n## Natural Alignment with Browser Behavior\n\nReact Router's handling of network concurrency is heavily inspired by the default behavior of web browsers when processing documents.\n\n### Link Navigation\n\n**Browser Behavior**: When you click on a link in a browser and then click on another before the page transition completes, the browser prioritizes the most recent `action`. It cancels the initial request, focusing solely on the latest link clicked.\n\n**React Router Behavior**: React Router manages client-side navigation the same way. When a link is clicked within a React Router application, it initiates fetch requests for each `loader` tied to the target URL. If another navigation interrupts the initial navigation, React Router cancels the previous fetch requests, ensuring that only the latest requests proceed.\n\n### Form Submission\n\n**Browser Behavior**: If you initiate a form submission in a browser and then quickly submit another form again, the browser disregards the first submission, processing only the latest one.\n\n**React Router Behavior**: React Router mimics this behavior when working with forms. If a form is submitted and another submission occurs before the first completes, React Router cancels the original fetch requests. It then waits for the latest submission to complete before triggering page revalidation again.\n\n## Concurrent Submissions and Revalidation\n\nWhile standard browsers are limited to one request at a time for navigations and form submissions, React Router elevates this behavior. Unlike navigation, with [`useFetcher`][use_fetcher] multiple requests can be in flight simultaneously.\n\nReact Router is designed to handle multiple form submissions to server `action`s and concurrent revalidation requests efficiently. It ensures that as soon as new data is available, the state is updated promptly. However, React Router also safeguards against potential pitfalls by refraining from committing stale data when other `action`s introduce race conditions.\n\nFor instance, if three form submissions are in progress, and one completes, React Router updates the UI with that data immediately without waiting for the other two so that the UI remains responsive and dynamic. As the remaining submissions finalize, React Router continues to update the UI, ensuring that the most recent data is displayed.\n\nUsing this key:\n\n- `|`: Submission begins\n- โœ“: Action complete, data revalidation begins\n- โœ…: Revalidated data is committed to the UI\n- โŒ: Request cancelled\n\nWe can visualize this scenario in the following diagram:\n\n```text\nsubmission 1: |----โœ“-----โœ…\nsubmission 2: |-----โœ“-----โœ…\nsubmission 3: |-----โœ“-----โœ…\n```\n\nHowever, if a subsequent submission's revalidation completes before an earlier one, React Router discards the earlier data, ensuring that only the most up-to-date information is reflected in the UI:\n\n```text\nsubmission 1: |----โœ“---------โŒ\nsubmission 2: |-----โœ“-----โœ…\nsubmission 3: |-----โœ“-----โœ…\n```\n\nBecause the revalidation from submission (2) started later and landed earlier than submission (1), the requests from submission (1) are canceled and only the data from submission (2) is committed to the UI. It was requested later, so it's more likely to contain the updated values from both (1) and (2).\n\n## Potential for Stale Data\n\nIt's unlikely your users will ever experience this, but there are still chances for the user to see stale data in very rare conditions with inconsistent infrastructure. Even though React Router cancels requests for stale data, they will still end up making it to the server. Canceling a request in the browser simply releases browser resources for that request; it can't \"catch up\" and stop it from getting to the server. In extremely rare conditions, a canceled request may change data after the interrupting `action`'s revalidation lands. Consider this diagram:\n\n```text\n ๐Ÿ‘‡ interruption with new submission\n|----โŒ----------------------โœ“\n |-------โœ“-----โœ…\n ๐Ÿ‘†\n initial request reaches the server\n after the interrupting submission\n has completed revalidation\n```\n\nThe user is now looking at different data than what is on the server. Note that this problem is both extremely rare and exists with default browser behavior, too. The chance of the initial request reaching the server later than both the submission and revalidation of the second is unexpected on any network and server infrastructure. If this is a concern with your infrastructure, you can send timestamps with your form submissions and write server logic to ignore stale submissions.\n\n## Example\n\nIn UI components like comboboxes, each keystroke can trigger a network request. Managing such rapid, consecutive requests can be tricky, especially when ensuring that the displayed results match the most recent query. However, with React Router, this challenge is automatically handled, ensuring that users see the correct results without developers having to micromanage the network.\n\n```tsx filename=app/pages/city-search.tsx\nexport async function loader({ request }) {\n const { searchParams } = new URL(request.url);\n const cities = await searchCities(searchParams.get(\"q\"));\n return cities;\n}\n\nexport function CitySearchCombobox() {\n const fetcher = useFetcher();\n\n return (\n \n \n \n // submit the form onChange to get the list of cities\n fetcher.submit(event.target.form)\n }\n />\n\n {/* render with the loader's data */}\n {fetcher.data ? (\n \n {fetcher.data.length > 0 ? (\n \n {fetcher.data.map((city) => (\n \n ))}\n \n ) : (\n No results found\n )}\n \n ) : null}\n \n \n );\n}\n```\n\nAll the application needs to know is how to query the data and how to render it. React Router handles the network.\n\n## Conclusion\n\nReact Router offers developers an intuitive, browser-based approach to managing network requests. By mirroring browser behaviors and enhancing them where needed, it simplifies the complexities of concurrency, revalidation, and potential race conditions. Whether you're building a simple webpage or a sophisticated web application, React Router ensures that your user interactions are smooth, reliable, and always up to date.\n\n[use_fetcher]: ../api/hooks/useFetcher\n" }, { "path": "docs/explanation/form-vs-fetcher.md", "content": "---\ntitle: Form vs. fetcher\n---\n\n# Form vs. fetcher\n\n[MODES: framework, data]\n\n## Overview\n\nDeveloping in React Router offers a rich set of tools that can sometimes overlap in functionality, creating a sense of ambiguity for newcomers. The key to effective development in React Router is understanding the nuances and appropriate use cases for each tool. This document seeks to provide clarity on when and why to use specific APIs.\n\n## APIs in Focus\n\n- [`
`][form-component]\n- [`useFetcher`][use-fetcher]\n- [`useNavigation`][use-navigation]\n\nUnderstanding the distinctions and intersections of these APIs is vital for efficient and effective React Router development.\n\n## URL Considerations\n\nThe primary criterion when choosing among these tools is whether you want the URL to change or not:\n\n- **URL Change Desired**: When navigating or transitioning between pages, or after certain actions like creating or deleting records. This ensures that the user's browser history accurately reflects their journey through your application.\n - **Expected Behavior**: In many cases, when users hit the back button, they should be taken to the previous page. Other times the history entry may be replaced but the URL change is important nonetheless.\n\n- **No URL Change Desired**: For actions that don't significantly change the context or primary content of the current view. This might include updating individual fields or minor data manipulations that don't warrant a new URL or page reload. This also applies to loading data with fetchers for things like popovers, combo boxes, etc.\n\n### When the URL Should Change\n\nThese actions typically reflect significant changes to the user's context or state:\n\n- **Creating a New Record**: After creating a new record, it's common to redirect users to a page dedicated to that new record, where they can view or further modify it.\n\n- **Deleting a Record**: If a user is on a page dedicated to a specific record and decides to delete it, the logical next step is to redirect them to a general page, such as a list of all records.\n\nFor these cases, developers should consider using a combination of [``][form-component] and [`useNavigation`][use-navigation]. These tools can be coordinated to handle form submission, invoke specific actions, retrieve action-related data through component props, and manage navigation respectively.\n\n### When the URL Shouldn't Change\n\nThese actions are generally more subtle and don't require a context switch for the user:\n\n- **Updating a Single Field**: Maybe a user wants to change the name of an item in a list or update a specific property of a record. This action is minor and doesn't necessitate a new page or URL.\n\n- **Deleting a Record from a List**: In a list view, if a user deletes an item, they likely expect to remain on the list view, with that item no longer in the list.\n\n- **Creating a Record in a List View**: When adding a new item to a list, it often makes sense for the user to remain in that context, seeing their new item added to the list without a full page transition.\n\n- **Loading Data for a Popover or Combobox**: When loading data for a popover or combobox, the user's context remains unchanged. The data is loaded in the background and displayed in a small, self-contained UI element.\n\nFor such actions, [`useFetcher`][use-fetcher] is the go-to API. It's versatile, combining functionalities of these APIs, and is perfectly suited for tasks where the URL should remain unchanged.\n\n## API Comparison\n\nAs you can see, the two sets of APIs have a lot of similarities:\n\n| Navigation/URL API | Fetcher API |\n| ----------------------------- | -------------------- |\n| `` | `` |\n| `actionData` (component prop) | `fetcher.data` |\n| `navigation.state` | `fetcher.state` |\n| `navigation.formAction` | `fetcher.formAction` |\n| `navigation.formData` | `fetcher.formData` |\n\n## Examples\n\n### Creating a New Record\n\n```tsx filename=app/pages/new-recipe.tsx lines=[16,23-24,29]\nimport {\n Form,\n redirect,\n useNavigation,\n} from \"react-router\";\nimport type { Route } from \"./+types/new-recipe\";\n\nexport async function action({\n request,\n}: Route.ActionArgs) {\n const formData = await request.formData();\n const errors = await validateRecipeFormData(formData);\n if (errors) {\n return { errors };\n }\n const recipe = await db.recipes.create(formData);\n return redirect(`/recipes/${recipe.id}`);\n}\n\nexport function NewRecipe({\n actionData,\n}: Route.ComponentProps) {\n const { errors } = actionData || {};\n const navigation = useNavigation();\n const isSubmitting =\n navigation.formAction === \"/recipes/new\";\n\n return (\n \n \n