Bump react-router-dom from 5.3.4 to 6.30.3
Type: Pull Request
State: Closed
Association: Unknown
Comments: 2
(5 months ago)
(5 months ago)
(5 months ago)
dependencies Stale javascript
Ericky14
Bumps react-router-dom from 5.3.4 to 6.30.3.
Release notes
Sourced from react-router-dom's releases.
v6.4.4
What's Changed
- Throw an error if an
action/loaderfunction returnsundefinedas revalidations need to know whether the loader has previously been executed.undefinedalso causes issues during SSR stringification for hydration. You should always ensure yourloader/actionreturns a value, and you may returnnullif you don't wish to return anything. (#9511)- Properly handle redirects to external domains (#9590, #9654)
- Preserve the HTTP method on 307/308 redirects (#9597)
- Support
basenamein static data routers (#9591)- Enhanced
ErrorResponsebodies to contain more descriptive text in internal 403/404/405 scenarios- Fix issues with encoded characters in
NavLinkand descendant<Routes>(#9589, #9647)- Properly serialize/deserialize
ErrorResponseinstances when using built-in hydration (#9593)- Support
basenamein static data routers (#9591)- Updated dependencies:
@remix-run/router@1.0.4react-router@6.4.4Full Changelog: https://github.com/remix-run/react-router/compare/react-router-dom@6.4.3...react-router-dom@6.4.4
react-router-dom@6.4.0-pre.15
Patch Changes
fix: remove internal router singleton (#9227)
This change removes the internal module-level
routerSingletonwe create and maintain inside our data routers since it was causing a number of headaches for non-simple use cases:
- Unit tests are a pain because you need to find a way to reset the singleton in-between tests
- Use use a
_resetModuleScopesingleton for our tests- ...but this isn't exposed to users who may want to do their own tests around our router
- The JSX children
<Route>objects cause non-intuitive behavior based on idiomatic react expectations
- Conditional runtime
<Route>'s won't get picked up- Adding new
<Route>'s during local dev won't get picked up during HMR- Using external state in your elements doesn't work as one might expect (see #9225)
Instead, we are going to lift the singleton out into user-land, so that they create the router singleton and manage it outside the react tree - which is what react 18 is encouraging with
useSyncExternalStoreanyways! This also means that since users create the router - there's no longer any difference in the rendering aspect for memory/browser/hash routers (which only impacts router/history creation) - so we can get rid of those and trim to a simpleRouterProvider// Before function App() { <DataBrowserRouter> <Route path="/" element={<Layout />}> <Route index element={<Home />}> </Route> <DataBrowserRouter> }// After let router = createBrowserRouter([{ path: "/", element: <Layout />, children: [{ index: true,
... (truncated)
Changelog
Sourced from react-router-dom's changelog.
v6.30.3
Date: 2026-01-07
Security Notice
This release addresses 1 security vulnerability:
Patch Changes
- Validate redirect locations (#14707)
Full Changelog:
v6.30.2...v6.30.3v6.30.2
Date: 2025-11-13
Security Notice
This release addresses 1 security vulnerability:
Patch Changes
- Normalize double-slashes in
resolvePath(#14537)Full Changelog:
v6.30.1...v6.30.2v6.30.1
Date: 2025-05-20
Patch Changes
- Partially revert optimization added in
6.29.0to reduce calls tomatchRoutesbecause it surfaced other issues (#13623)- Stop logging invalid warning when
v7_relativeSplatPathis set tofalse(#13502)Full Changelog:
v6.30.0...v6.30.1v6.30.0
Date: 2025-02-27
Minor Changes
- Add
fetcherKeyas a parameter topatchRoutesOnNavigation(#13109)
... (truncated)
Commits
c662ca3chore: Update version for release (#14713)98ad691chore: Update version for release (pre-v6) (#14710)26b5d45chore: Update version for release (#14541)919f8a8chore: Update version for release (pre-v6) (#14540)3f2400echore: Update version for release (#13647)25a264dchore: Update version for release (pre-v6) (#13638)e4ba522chore: Update version for release (#13128)f0bc784chore: Update version for release (pre-v6) (#13111)d9ed824Fix up changelogscc8b8cechore: Update version for release (#12911)- Additional commits viewable in compare view
Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for react-router-dom since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Package Dependencies
Security Advisories
React Router vulnerable to XSS via Open Redirects
React Router has unexpected external redirect via untrusted paths
Technical Details
| ID: | 12813937 |
| UUID: | 3805014435 |
| Node ID: | PR_kwDOCwz4yM68vIrE |
| Host: | GitHub |
| Repository: | codeparticle/codeparticle.website.process |