Rename unstable_patchRoutesOnMiss to unstable_patchRoutesOnNavigation to match new behavior (#11888)
Updated dependencies:
@remix-run/router@1.19.1
6.26.0
Minor Changes
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)
Patch Changes
Fix initial hydration behavior when using future.v7_partialHydration along with unstable_patchRoutesOnMiss (#11838)
During initial hydration, router.state.matches will now include any partial matches so that we can render ancestor HydrateFallback components
Updated dependencies:
@remix-run/router@1.19.0
6.25.1
No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v6.25.1.
6.25.0
Minor Changes
Stabilize future.unstable_skipActionErrorRevalidation as future.v7_skipActionErrorRevalidation (#11769)
When this flag is enabled, actions will not automatically trigger a revalidation if they return/throw a Response with a 4xx/5xx status code
You may still opt-into revalidation via shouldRevalidate
This also changes shouldRevalidate's unstable_actionStatus parameter to actionStatus
Patch Changes
Fix regression and properly decode paths inside useMatch so matches/params reflect decoded params (#11789)
Throw an error if an action/loader function returns undefined as revalidations need to know whether the loader has previously been executed. undefined also causes issues during SSR stringification for hydration. You should always ensure your loader/action returns a value, and you may return null if 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)
This change removes the internal module-level routerSingleton we 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 _resetModuleScope singleton 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 useSyncExternalStore anyways! 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 simple RouterProvider
// Before
function App() {
<DataBrowserRouter>
<Route path="/" element={<Layout />}>
<Route index element={<Home />}>
</Route>
<DataBrowserRouter>
}
// After
let router = createBrowserRouter([{
path: "/",
element: <Layout />,
children: [{
index: true,
Rename unstable_patchRoutesOnMiss to unstable_patchRoutesOnNavigation to match new behavior (#11888)
Updated dependencies:
@remix-run/router@1.19.1
react-router@6.26.1
6.26.0
Minor Changes
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)
Patch Changes
Fix initial hydration behavior when using future.v7_partialHydration along with unstable_patchRoutesOnMiss (#11838)
During initial hydration, router.state.matches will now include any partial matches so that we can render ancestor HydrateFallback components
Updated dependencies:
@remix-run/router@1.19.0
react-router@6.26.0
6.25.1
Patch Changes
Memoize some RouterProvider internals to reduce unnecessary re-renders (#11803)
Updated dependencies:
react-router@6.25.1
6.25.0
Minor Changes
Stabilize future.unstable_skipActionErrorRevalidation as future.v7_skipActionErrorRevalidation (#11769)
When this flag is enabled, actions will not automatically trigger a revalidation if they return/throw a Response with a 4xx/5xx status code
You may still opt-into revalidation via shouldRevalidate
This also changes shouldRevalidate's unstable_actionStatus parameter to actionStatus
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 rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/sienori/Tab-Session-Manager/network/alerts).
Removes path-to-regexp. It's no longer used after updating ancestor dependencies path-to-regexp, react-router and react-router-dom. These dependencies need to be updated together.
Removes
path-to-regexpUpdates
react-routerfrom 5.1.2 to 6.26.2Release notes
Sourced from react-router's releases.
... (truncated)
Changelog
Sourced from react-router's changelog.
... (truncated)
Commits
eeb86abchore: Update version for release (#11968)7cbe349chore: Update version for release (pre) (#11955)6483515Merge branch 'release-next' into v605612a3unstable_dataStrategy refactor for better single fetch support (#11943)04d09c3chore: Update version for release (#11895)f806fa4chore: Update version for release (pre) (#11889)5a6545bRename patchRoutesOnMiss to patchRoutesOnNavigation (#11888)91ef146chore: Update version for release (#11863)7acbfbechore: Update version for release (pre) (#11860)8334033chore: Update version for release (pre) (#11854)Updates
react-router-domfrom 5.1.2 to 6.26.2Release notes
Sourced from react-router-dom's releases.
... (truncated)
Changelog
Sourced from react-router-dom's changelog.
... (truncated)
Commits
eeb86abchore: Update version for release (#11968)7cbe349chore: Update version for release (pre) (#11955)6483515Merge branch 'release-next' into v605612a3unstable_dataStrategy refactor for better single fetch support (#11943)5651176fix: Wait for restore url navigation to complete before proceeding (#11930)04d09c3chore: Update version for release (#11895)f806fa4chore: Update version for release (pre) (#11889)5a6545bRename patchRoutesOnMiss to patchRoutesOnNavigation (#11888)91ef146chore: Update version for release (#11863)7acbfbechore: Update version for release (pre) (#11860)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 rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show