Overview - Router

router

7 days30 days

Latest CI Pipeline Executions

Exact

Succeeded
main
dbfea0d0 docs(router): simplify route variable naming in search params guide (#3890) In the "search params" guide, the usage of the variable `allProductsRoute` has been changed to `Route` in the code-block examples for consistency and clarity. This makes the examples easier to follow since `Route` is used throughout the rest of the documentation.
4 hours ago by ehtishamsa...
Failed
main
dbfea0d0 docs(router): simplify route variable naming in search params guide (#3890) In the "search params" guide, the usage of the variable `allProductsRoute` has been changed to `Route` in the code-block examples for consistency and clarity. This makes the examples easier to follow since `Route` is used throughout the rest of the documentation.
4 hours ago by ehtishamsa...
Succeeded
main
dbfea0d0 docs(router): simplify route variable naming in search params guide (#3890) In the "search params" guide, the usage of the variable `allProductsRoute` has been changed to `Route` in the code-block examples for consistency and clarity. This makes the examples easier to follow since `Route` is used throughout the rest of the documentation.
7 hours ago by ehtishamsa...
Succeeded
main
dbfea0d0 docs(router): simplify route variable naming in search params guide (#3890) In the "search params" guide, the usage of the variable `allProductsRoute` has been changed to `Route` in the code-block examples for consistency and clarity. This makes the examples easier to follow since `Route` is used throughout the rest of the documentation.
8 hours ago by ehtishamsa...
Failed
main
dbfea0d0 docs(router): simplify route variable naming in search params guide (#3890) In the "search params" guide, the usage of the variable `allProductsRoute` has been changed to `Route` in the code-block examples for consistency and clarity. This makes the examples easier to follow since `Route` is used throughout the rest of the documentation.
13 hours ago by ehtishamsa...
Failed
main
9ca08f47 release: v1.114.32
13 hours ago by tannerlinsley
Succeeded
main
9ca08f47 release: v1.114.32
15 hours ago by tannerlinsley
Succeeded
main
fb99d92c fix(router-core): remove `React` type dependency (#3902)
19 hours ago by chorobin
Succeeded
main
eab355aa docs: Fix HeadContent docs (#3905) ## Changes 1. **Fix createRootRoute syntax**: Updated all examples in the document head management guide to use the correct `createRootRoute({...})` syntax instead of the incorrect `createRootRoute()({...})` syntax. 2. **Fix HeadContent placement**: The previous commit corrected the code example for Single-Page Applications to properly show the correct syntax for creating a root route with HeadContent. ## Why these changes matter - The incorrect syntax examples could lead to confusion for developers implementing document head management in their applications - These fixes ensure consistency throughout the documentation and provide developers with the correct implementation patterns - Proper documentation helps reduce support requests and improves developer experience ## Technical details - Fixed 5 instances of incorrect `createRootRoute()({...})` syntax throughout the document - Previously fixed the SPA example which had an incorrect API reference These changes ensure that all code examples in the document head management guide are correct and consistent with the actual API implementation.
19 hours ago by diegogb-08
Succeeded
main
eab355aa docs: Fix HeadContent docs (#3905) ## Changes 1. **Fix createRootRoute syntax**: Updated all examples in the document head management guide to use the correct `createRootRoute({...})` syntax instead of the incorrect `createRootRoute()({...})` syntax. 2. **Fix HeadContent placement**: The previous commit corrected the code example for Single-Page Applications to properly show the correct syntax for creating a root route with HeadContent. ## Why these changes matter - The incorrect syntax examples could lead to confusion for developers implementing document head management in their applications - These fixes ensure consistency throughout the documentation and provide developers with the correct implementation patterns - Proper documentation helps reduce support requests and improves developer experience ## Technical details - Fixed 5 instances of incorrect `createRootRoute()({...})` syntax throughout the document - Previously fixed the SPA example which had an incorrect API reference These changes ensure that all code examples in the document head management guide are correct and consistent with the actual API implementation.
1 day ago by diegogb-08
Succeeded
main
1bbe4a06 docs(router): correct ReturnType of `Router.matchRoute` to match the runtime output (#3896) The `.matchRoute` method on the Router type page previously stated it returns a `RouteMatch` object. In reality, it returns only the route match's params. This update corrects the return type in docs to reflect actual behavior. Fix #3875
1 day ago by Redbird10
Succeeded
main
1bbe4a06 docs(router): correct ReturnType of `Router.matchRoute` to match the runtime output (#3896) The `.matchRoute` method on the Router type page previously stated it returns a `RouteMatch` object. In reality, it returns only the route match's params. This update corrects the return type in docs to reflect actual behavior. Fix #3875
1 day ago by Redbird10
Succeeded
main
d0bbf662 chore(deps): update dependency vite to v6.1.3 [security] (#3900) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [vite](https://vite.dev) ([source](https://redirect.github.com/vitejs/vite/tree/HEAD/packages/vite)) | [`6.1.2` -> `6.1.3`](https://renovatebot.com/diffs/npm/vite/6.1.2/6.1.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/vite/6.1.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/vite/6.1.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/vite/6.1.2/6.1.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/vite/6.1.2/6.1.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | ### GitHub Vulnerability Alerts #### [CVE-2025-31125](https://redirect.github.com/vitejs/vite/security/advisories/GHSA-4r4m-qw57-chr8) ### Summary The contents of arbitrary files can be returned to the browser. ### Impact Only apps explicitly exposing the Vite dev server to the network (using `--host` or [`server.host` config option](https://vitejs.dev/config/server-options.html#server-host)) are affected. ### Details - base64 encoded content of non-allowed files is exposed using `?inline&import` (originally reported as `?import&?inline=1.wasm?init`) - content of non-allowed files is exposed using `?raw?import` `/@fs/` isn't needed to reproduce the issue for files inside the project root. ### PoC Original report (check details above for simplified cases): The ?import&?inline=1.wasm?init ending allows attackers to read arbitrary files and returns the file content if it exists. Base64 decoding needs to be performed twice ``` $ npm create vite@latest $ cd vite-project/ $ npm install $ npm run dev ``` Example full URL `http://localhost:5173/@fs/C:/windows/win.ini?import&?inline=1.wasm?init` --- ### Release Notes <details> <summary>vitejs/vite (vite)</summary> ### [`v6.1.3`](https://redirect.github.com/vitejs/vite/releases/tag/v6.1.3) [Compare Source](https://redirect.github.com/vitejs/vite/compare/v6.1.2...v6.1.3) Please refer to [CHANGELOG.md](https://redirect.github.com/vitejs/vite/blob/v6.1.3/packages/vite/CHANGELOG.md) for details. </details> --- ### Configuration 📅 **Schedule**: Branch creation - "" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/TanStack/router).  Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
1 day ago by renovate[bot]
Succeeded
main
e9b253eb fix(router-plugin): code-splitting to handle default exported function declarations (#3901) Currently, when the code-splitter encounters a known identifier used for configuration in `createFileRoute` (such as `component`, `loader`, `errorComponent`, etc.) it retains the export without splitting it out into a separate file. This functionality is currently partially working when the export is a "default export" which references an already declared identifier. ```ts const loader = () => {} export default loader ``` However, it does not work when the "default export" is also making a function declaration for the export. ```ts export default function loader() {} ``` This PR adds the functionality to detect this use case and perform the same transformations to align itself with the behaviour for all others exports.
1 day ago by SeanCassiere
Succeeded
main
0394b6b6 fix(router-devtools-core): remove floating panel style on close (#3898)
2 days ago by birkskyum
Failed
main
0394b6b6 fix(router-devtools-core): remove floating panel style on close (#3898)
2 days ago by birkskyum
Failed
main
0394b6b6 fix(router-devtools-core): remove floating panel style on close (#3898)
2 days ago by birkskyum
Succeeded
main
1f2e2435 docs(start): add note on needing variable export named as `APIRoute` (#3892) Just a quick note to prevent hitting 404s where the export needs to be named `APIRoute`. --------- Co-authored-by: Sean Cassiere <33615041+SeanCassiere@users.noreply.github.com>
2 days ago by AtAFork
Failed
main
1f2e2435 docs(start): add note on needing variable export named as `APIRoute` (#3892) Just a quick note to prevent hitting 404s where the export needs to be named `APIRoute`. --------- Co-authored-by: Sean Cassiere <33615041+SeanCassiere@users.noreply.github.com>
2 days ago by AtAFork
Failed
main
1f2e2435 docs(start): add note on needing variable export named as `APIRoute` (#3892) Just a quick note to prevent hitting 404s where the export needs to be named `APIRoute`. --------- Co-authored-by: Sean Cassiere <33615041+SeanCassiere@users.noreply.github.com>
2 days ago by AtAFork