build(deps): bump react-router-dom from 5.3.4 to 6.23.0
Bumps react-router-dom from 5.3.4 to 6.23.0.
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/[email protected][email protected]Full Changelog: https://github.com/remix-run/react-router/compare/[email protected]@6.4.4
[email protected]
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.
6.23.0
Minor Changes
- Add a new
unstable_dataStrategyconfiguration option (#11098)
- This option allows Data Router applications to take control over the approach for executing route loaders and actions
- 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, middleware/context APIs, automatic loader caching, and more
Patch Changes
- Updated dependencies:
@remix-run/[email protected][email protected]6.22.3
Patch Changes
- Updated dependencies:
@remix-run/[email protected][email protected]6.22.2
Patch Changes
- Updated dependencies:
@remix-run/[email protected][email protected]6.22.1
Patch Changes
- Updated dependencies:
[email protected]@remix-run/[email protected]6.22.0
Minor Changes
- Include a
window__reactRouterVersiontag for CWV Report detection (#11222)Patch Changes
- Updated dependencies:
@remix-run/[email protected][email protected]
... (truncated)
Commits
82a3a77chore: Update version for release (#11486)8a20f32chore: Update version for release (pre) (#11387)88ec71achore: Update version for release (pre) (#11379)12afb2eMigrate to pnpm (#11358)c7dd3d3Data Strategy Configuration (#11098)67009e1chore: Update version for release (#11329)0c37f37chore: Update version for release (pre) (#11327)78c843bchore: Update version for release (#11314)e1421bechore: Update version for release (pre) (#11309)95acd38Merge branch 'release-next' into dev- Additional commits viewable in compare view
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)