From 08467f9dac8433818d3f3fcd3372f0f957fa85be Mon Sep 17 00:00:00 2001
From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com>
Date: Sat, 6 May 2023 14:21:15 +0000
Subject: [PATCH] chore(deps): update react-router monorepo to v6.11.0 (#3703)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
[](https://renovatebot.com)
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [react-router](https://togithub.com/remix-run/react-router) | [`6.8.1`
->
`6.11.0`](https://renovatebot.com/diffs/npm/react-router/6.8.1/6.11.0) |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
| [react-router-dom](https://togithub.com/remix-run/react-router) |
[`6.8.1` ->
`6.11.0`](https://renovatebot.com/diffs/npm/react-router-dom/6.8.1/6.11.0)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
---
### Release Notes
remix-run/react-router (react-router)
###
[`v6.11.0`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router/CHANGELOG.md#6110)
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router@6.10.0...react-router@6.11.0)
##### Patch Changes
- Log loader/action errors to the console in dev for easier stack trace
evaluation
([#10286](https://togithub.com/remix-run/react-router/pull/10286))
- Fix bug preventing rendering of descendant `` when
`RouterProvider` errors existed
([#10374](https://togithub.com/remix-run/react-router/pull/10374))
- Fix inadvertent re-renders when using `Component` instead of `element`
on a route definition
([#10287](https://togithub.com/remix-run/react-router/pull/10287))
- 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://togithub.com/remix-run/react-router/pull/10394))
- 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 footguns in `useEffect` calls.
([#10377](https://togithub.com/remix-run/react-router/pull/10377),
[#10409](https://togithub.com/remix-run/react-router/pull/10409))
- Allow `useRevalidator()` to resolve a loader-driven error boundary
scenario
([#10369](https://togithub.com/remix-run/react-router/pull/10369))
- Avoid unnecessary unsubscribe/resubscribes on router state changes
([#10409](https://togithub.com/remix-run/react-router/pull/10409))
- 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()`. When using `BrowserRouter`, these hooks remain unstable
across location changes because they still rely on `useLocation()`.
([#10336](https://togithub.com/remix-run/react-router/pull/10336))
- Updated dependencies:
- `@remix-run/router@1.6.0`
###
[`v6.10.0`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router/CHANGELOG.md#6100)
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router@6.9.0...react-router@6.10.0)
##### Minor Changes
- Added support for [**Future
Flags**](https://reactrouter.com/en/main/guides/api-development-strategy)
in React Router. The first 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()` behavior.
([#10207](https://togithub.com/remix-run/react-router/pull/10207))
- When `future.v7_normalizeFormMethod === false` (default v6 behavior),
- `useNavigation().formMethod` is lowercase
- `useFetcher().formMethod` is lowercase
- When `future.v7_normalizeFormMethod === true`:
- `useNavigation().formMethod` is uppercase
- `useFetcher().formMethod` is uppercase
##### Patch Changes
- Fix route ID generation when using Fragments in
`createRoutesFromElements`
([#10193](https://togithub.com/remix-run/react-router/pull/10193))
- Updated dependencies:
- `@remix-run/router@1.5.0`
###
[`v6.9.0`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router/CHANGELOG.md#690)
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router@6.8.2...react-router@6.9.0)
##### Minor Changes
- React 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".
([#10045](https://togithub.com/remix-run/react-router/pull/10045))
**Example JSON Syntax**
```jsx
// Both of these work the same:
const elementRoutes = [{
path: '/',
element: ,
errorElement: ,
}]
const componentRoutes = [{
path: '/',
Component: Home,
ErrorBoundary: HomeError,
}]
function Home() { ... }
function HomeError() { ... }
```
**Example JSX Syntax**
```jsx
// Both of these work the same:
const elementRoutes = createRoutesFromElements(
} errorElement={ } />
);
const componentRoutes = createRoutesFromElements(
);
function Home() { ... }
function HomeError() { ... }
```
- **Introducing Lazy Route Modules!**
([#10045](https://togithub.com/remix-run/react-router/pull/10045))
In 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`).
Lazy 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.
Your `lazy` functions will typically return the result of a dynamic
import.
```jsx
// In this example, we assume most folks land on the homepage so we
include that
// in our critical-path bundle, but then we lazily load modules for /a
and /b so
// they don't load until the user navigates to those routes
let routes = createRoutesFromElements(
}>
} />
import("./a")} />
import("./b")} />
);
```
Then in your lazy route modules, export the properties you want defined
for the route:
```jsx
export async function loader({ request }) {
let data = await fetchData(request);
return json(data);
}
// Export a `Component` directly instead of needing to create a React
Element from it
export function Component() {
let data = useLoaderData();
return (
<>
You made it!
{data}
);
}
// Export an `ErrorBoundary` directly instead of needing to create a
React Element from it
export function ErrorBoundary() {
let error = useRouteError();
return isRouteErrorResponse(error) ? (
{error.status} {error.statusText}
) : (
{error.message || error}
);
}
```
An example of this in action can be found in the
[`examples/lazy-loading-router-provider`](https://togithub.com/remix-run/react-router/tree/main/examples/lazy-loading-router-provider)
directory of the repository.
🙌 Huge thanks to [@rossipedia](https://togithub.com/rossipedia)
for the [Initial
Proposal](https://togithub.com/remix-run/react-router/discussions/9826)
and [POC
Implementation](https://togithub.com/remix-run/react-router/pull/9830).
- Updated dependencies:
- `@remix-run/router@1.4.0`
##### Patch Changes
- Fix `generatePath` incorrectly applying parameters in some cases
([#10078](https://togithub.com/remix-run/react-router/pull/10078))
- Improve memoization for context providers to avoid unnecessary
re-renders
([#9983](https://togithub.com/remix-run/react-router/pull/9983))
###
[`v6.8.2`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router/CHANGELOG.md#682)
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router@6.8.1...react-router@6.8.2)
##### Patch Changes
- Updated dependencies:
- `@remix-run/router@1.3.3`
remix-run/react-router (react-router-dom)
###
[`v6.11.0`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6110)
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router-dom@6.10.0...react-router-dom@6.11.0)
##### Minor Changes
- Enable `basename` support in `useFetcher`
([#10336](https://togithub.com/remix-run/react-router/pull/10336))
- 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')`)
##### Patch Changes
- Fix inadvertent re-renders when using `Component` instead of `element`
on a route definition
([#10287](https://togithub.com/remix-run/react-router/pull/10287))
- Fail gracefully on `` and other invalid URL values
([#10367](https://togithub.com/remix-run/react-router/pull/10367))
- 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 footguns in `useEffect` calls.
([#10377](https://togithub.com/remix-run/react-router/pull/10377),
[#10409](https://togithub.com/remix-run/react-router/pull/10409))
- Add static prop to `StaticRouterProvider`'s internal `Router`
component
([#10401](https://togithub.com/remix-run/react-router/pull/10401))
- 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()`. When using `BrowserRouter`, these hooks remain unstable
across location changes because they still rely on `useLocation()`.
([#10336](https://togithub.com/remix-run/react-router/pull/10336))
- Updated dependencies:
- `react-router@6.11.0`
- `@remix-run/router@1.6.0`
###
[`v6.10.0`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6100)
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router-dom@6.9.0...react-router-dom@6.10.0)
##### Minor Changes
- Added support for [**Future
Flags**](https://reactrouter.com/en/main/guides/api-development-strategy)
in React Router. The first 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()` behavior.
([#10207](https://togithub.com/remix-run/react-router/pull/10207))
- When `future.v7_normalizeFormMethod === false` (default v6 behavior),
- `useNavigation().formMethod` is lowercase
- `useFetcher().formMethod` is lowercase
- When `future.v7_normalizeFormMethod === true`:
- `useNavigation().formMethod` is uppercase
- `useFetcher().formMethod` is uppercase
##### Patch Changes
- Fix `createStaticHandler` to also check for `ErrorBoundary` on routes
in addition to `errorElement`
([#10190](https://togithub.com/remix-run/react-router/pull/10190))
- Updated dependencies:
- `@remix-run/router@1.5.0`
- `react-router@6.10.0`
###
[`v6.9.0`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#690)
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router-dom@6.8.2...react-router-dom@6.9.0)
##### Minor Changes
- React 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".
([#10045](https://togithub.com/remix-run/react-router/pull/10045))
**Example JSON Syntax**
```jsx
// Both of these work the same:
const elementRoutes = [{
path: '/',
element: ,
errorElement: ,
}]
const componentRoutes = [{
path: '/',
Component: Home,
ErrorBoundary: HomeError,
}]
function Home() { ... }
function HomeError() { ... }
```
**Example JSX Syntax**
```jsx
// Both of these work the same:
const elementRoutes = createRoutesFromElements(
} errorElement={ } />
);
const componentRoutes = createRoutesFromElements(
);
function Home() { ... }
function HomeError() { ... }
```
- **Introducing Lazy Route Modules!**
([#10045](https://togithub.com/remix-run/react-router/pull/10045))
In 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`).
Lazy 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.
Your `lazy` functions will typically return the result of a dynamic
import.
```jsx
// In this example, we assume most folks land on the homepage so we
include that
// in our critical-path bundle, but then we lazily load modules for /a
and /b so
// they don't load until the user navigates to those routes
let routes = createRoutesFromElements(
}>
} />
import("./a")} />
import("./b")} />
);
```
Then in your lazy route modules, export the properties you want defined
for the route:
```jsx
export async function loader({ request }) {
let data = await fetchData(request);
return json(data);
}
// Export a `Component` directly instead of needing to create a React
Element from it
export function Component() {
let data = useLoaderData();
return (
<>
You made it!
{data}
);
}
// Export an `ErrorBoundary` directly instead of needing to create a
React Element from it
export function ErrorBoundary() {
let error = useRouteError();
return isRouteErrorResponse(error) ? (
{error.status} {error.statusText}
) : (
{error.message || error}
);
}
```
An example of this in action can be found in the
[`examples/lazy-loading-router-provider`](https://togithub.com/remix-run/react-router/tree/main/examples/lazy-loading-router-provider)
directory of the repository.
🙌 Huge thanks to [@rossipedia](https://togithub.com/rossipedia)
for the [Initial
Proposal](https://togithub.com/remix-run/react-router/discussions/9826)
and [POC
Implementation](https://togithub.com/remix-run/react-router/pull/9830).
- Updated dependencies:
- `react-router@6.9.0`
- `@remix-run/router@1.4.0`
###
[`v6.8.2`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#682)
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router-dom@6.8.1...react-router-dom@6.8.2)
##### Patch Changes
- Treat same-origin absolute URLs in `` as external if they are
outside of the router `basename`
([#10135](https://togithub.com/remix-run/react-router/pull/10135))
- Fix `useBlocker` to return `IDLE_BLOCKER` during SSR
([#10046](https://togithub.com/remix-run/react-router/pull/10046))
- Fix SSR of absolute `` urls
([#10112](https://togithub.com/remix-run/react-router/pull/10112))
- Properly escape HTML characters in `StaticRouterProvider` serialized
hydration data
([#10068](https://togithub.com/remix-run/react-router/pull/10068))
- Updated dependencies:
- `@remix-run/router@1.3.3`
- `react-router@6.8.2`
---
### Configuration
📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).
🚦 **Automerge**: Enabled.
â™» **Rebasing**: Whenever PR becomes conflicted, 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 has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://app.renovatebot.com/dashboard#github/Unleash/unleash).
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
---
frontend/package.json | 2 +-
frontend/yarn.lock | 30 +++++++++++++++---------------
website/package.json | 2 +-
website/yarn.lock | 18 +++++++++---------
4 files changed, 26 insertions(+), 26 deletions(-)
diff --git a/frontend/package.json b/frontend/package.json
index e9e9dab9cd..2dbc5a5104 100644
--- a/frontend/package.json
+++ b/frontend/package.json
@@ -98,7 +98,7 @@
"react-joyride": "^2.5.3",
"react-linkify": "^1.0.0-alpha",
"react-markdown": "^8.0.4",
- "react-router-dom": "6.8.1",
+ "react-router-dom": "6.11.0",
"react-table": "7.8.0",
"react-test-renderer": "17.0.2",
"react-timeago": "7.1.0",
diff --git a/frontend/yarn.lock b/frontend/yarn.lock
index 4810824b8a..22556220ab 100644
--- a/frontend/yarn.lock
+++ b/frontend/yarn.lock
@@ -2001,10 +2001,10 @@
resolved "https://registry.yarnpkg.com/@popperjs/core/-/core-2.11.6.tgz#cee20bd55e68a1720bdab363ecf0c821ded4cd45"
integrity sha512-50/17A98tWUfQ176raKiOGXuYpLyyVMkxxG6oylzL3BPOlA6ADGdK7EYunSa4I064xerltq9TGXs8HmOk5E+vw==
-"@remix-run/router@1.3.2":
- version "1.3.2"
- resolved "https://registry.yarnpkg.com/@remix-run/router/-/router-1.3.2.tgz#58cd2bd25df2acc16c628e1b6f6150ea6c7455bc"
- integrity sha512-t54ONhl/h75X94SWsHGQ4G/ZrCEguKSRQr7DrjTciJXW0YU1QhlwYeycvK5JgkzlxmvrK7wq1NB/PLtHxoiDcA==
+"@remix-run/router@1.6.0":
+ version "1.6.0"
+ resolved "https://registry.yarnpkg.com/@remix-run/router/-/router-1.6.0.tgz#45010e1826f4d81a1b2cfaf874f1aac93998cd28"
+ integrity sha512-N13NRw3T2+6Xi9J//3CGLsK2OqC8NMme3d/YX+nh05K9YHWGcv8DycHJrqGScSP4T75o8IN6nqIMhVFU8ohg8w==
"@rollup/plugin-commonjs@~22.0.2":
version "22.0.2"
@@ -7900,20 +7900,20 @@ react-refresh@^0.14.0:
resolved "https://registry.yarnpkg.com/react-refresh/-/react-refresh-0.14.0.tgz#4e02825378a5f227079554d4284889354e5f553e"
integrity sha512-wViHqhAd8OHeLS/IRMJjTSDHF3U9eWi62F/MledQGPdJGDhodXJ9PBLNGr6WWL7qlH12Mt3TyTpbS+hGXMjCzQ==
-react-router-dom@6.8.1:
- version "6.8.1"
- resolved "https://registry.yarnpkg.com/react-router-dom/-/react-router-dom-6.8.1.tgz#7e136b67d9866f55999e9a8482c7008e3c575ac9"
- integrity sha512-67EXNfkQgf34P7+PSb6VlBuaacGhkKn3kpE51+P6zYSG2kiRoumXEL6e27zTa9+PGF2MNXbgIUHTVlleLbIcHQ==
+react-router-dom@6.11.0:
+ version "6.11.0"
+ resolved "https://registry.yarnpkg.com/react-router-dom/-/react-router-dom-6.11.0.tgz#e9507327dad2dfdd3c4815810dbd8de8fc2ee211"
+ integrity sha512-Q3mK1c/CYoF++J6ZINz7EZzwlgSOZK/kc7lxIA7PhtWhKju4KfF1WHqlx0kVCIFJAWztuYVpXZeljEbds8z4Og==
dependencies:
- "@remix-run/router" "1.3.2"
- react-router "6.8.1"
+ "@remix-run/router" "1.6.0"
+ react-router "6.11.0"
-react-router@6.8.1:
- version "6.8.1"
- resolved "https://registry.yarnpkg.com/react-router/-/react-router-6.8.1.tgz#e362caf93958a747c649be1b47cd505cf28ca63e"
- integrity sha512-Jgi8BzAJQ8MkPt8ipXnR73rnD7EmZ0HFFb7jdQU24TynGW1Ooqin2KVDN9voSC+7xhqbbCd2cjGUepb6RObnyg==
+react-router@6.11.0:
+ version "6.11.0"
+ resolved "https://registry.yarnpkg.com/react-router/-/react-router-6.11.0.tgz#2e9008e40f8ce69e381373a7916ebadfbf2ff184"
+ integrity sha512-hTm6KKNpj9SDG4syIWRjCU219O0RZY8RUPobCFt9p+PlF7nnkRgMoh2DieTKvw3F3Mw6zg565HGnSv8BuoY5oQ==
dependencies:
- "@remix-run/router" "1.3.2"
+ "@remix-run/router" "1.6.0"
react-shallow-renderer@^16.13.1:
version "16.15.0"
diff --git a/website/package.json b/website/package.json
index 7fd4e92c52..08e2b1ee55 100644
--- a/website/package.json
+++ b/website/package.json
@@ -80,7 +80,7 @@
"@tsconfig/docusaurus": "1.0.7",
"babel-loader": "9.1.2",
"enhanced-resolve": "5.13.0",
- "react-router": "6.8.1",
+ "react-router": "6.11.0",
"replace-in-file": "6.3.5",
"storybook-addon-root-attribute": "1.0.2",
"typescript": "4.8.4"
diff --git a/website/yarn.lock b/website/yarn.lock
index 622b11229b..880332192b 100644
--- a/website/yarn.lock
+++ b/website/yarn.lock
@@ -2355,10 +2355,10 @@
redux-thunk "^2.4.2"
reselect "^4.1.7"
-"@remix-run/router@1.3.2":
- version "1.3.2"
- resolved "https://registry.yarnpkg.com/@remix-run/router/-/router-1.3.2.tgz#58cd2bd25df2acc16c628e1b6f6150ea6c7455bc"
- integrity sha512-t54ONhl/h75X94SWsHGQ4G/ZrCEguKSRQr7DrjTciJXW0YU1QhlwYeycvK5JgkzlxmvrK7wq1NB/PLtHxoiDcA==
+"@remix-run/router@1.6.0":
+ version "1.6.0"
+ resolved "https://registry.yarnpkg.com/@remix-run/router/-/router-1.6.0.tgz#45010e1826f4d81a1b2cfaf874f1aac93998cd28"
+ integrity sha512-N13NRw3T2+6Xi9J//3CGLsK2OqC8NMme3d/YX+nh05K9YHWGcv8DycHJrqGScSP4T75o8IN6nqIMhVFU8ohg8w==
"@sideway/address@^4.1.3":
version "4.1.4"
@@ -12671,12 +12671,12 @@ react-router@5.3.4, react-router@^5.3.3:
tiny-invariant "^1.0.2"
tiny-warning "^1.0.0"
-react-router@6.8.1:
- version "6.8.1"
- resolved "https://registry.yarnpkg.com/react-router/-/react-router-6.8.1.tgz#e362caf93958a747c649be1b47cd505cf28ca63e"
- integrity sha512-Jgi8BzAJQ8MkPt8ipXnR73rnD7EmZ0HFFb7jdQU24TynGW1Ooqin2KVDN9voSC+7xhqbbCd2cjGUepb6RObnyg==
+react-router@6.11.0:
+ version "6.11.0"
+ resolved "https://registry.yarnpkg.com/react-router/-/react-router-6.11.0.tgz#2e9008e40f8ce69e381373a7916ebadfbf2ff184"
+ integrity sha512-hTm6KKNpj9SDG4syIWRjCU219O0RZY8RUPobCFt9p+PlF7nnkRgMoh2DieTKvw3F3Mw6zg565HGnSv8BuoY5oQ==
dependencies:
- "@remix-run/router" "1.3.2"
+ "@remix-run/router" "1.6.0"
react-textarea-autosize@^8.3.2:
version "8.4.0"