react-router-dom 6.11.0-pre.2 → 6.11.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +7 -27
- package/dist/index.js +1 -1
- package/dist/main.js +1 -1
- package/dist/react-router-dom.development.js +1 -1
- package/dist/react-router-dom.production.min.js +1 -1
- package/dist/umd/react-router-dom.development.js +1 -1
- package/dist/umd/react-router-dom.production.min.js +1 -1
- package/package.json +3 -3
package/CHANGELOG.md
CHANGED
|
@@ -1,42 +1,22 @@
|
|
|
1
1
|
# `react-router-dom`
|
|
2
2
|
|
|
3
|
-
## 6.11.0
|
|
4
|
-
|
|
5
|
-
### Patch Changes
|
|
6
|
-
|
|
7
|
-
- Updated dependencies:
|
|
8
|
-
- `react-router@6.11.0-pre.2`
|
|
9
|
-
|
|
10
|
-
## 6.11.0-pre.1
|
|
11
|
-
|
|
12
|
-
### Patch Changes
|
|
13
|
-
|
|
14
|
-
- Add static prop to `StaticRouterProvider`'s internal `Router` component ([#10401](https://github.com/remix-run/react-router/pull/10401))
|
|
15
|
-
- Updated dependencies:
|
|
16
|
-
- `react-router@6.11.0-pre.1`
|
|
17
|
-
|
|
18
|
-
## 6.11.0-pre.0
|
|
3
|
+
## 6.11.0
|
|
19
4
|
|
|
20
5
|
### Minor Changes
|
|
21
6
|
|
|
22
|
-
-
|
|
23
|
-
|
|
24
|
-
- Example: `router.navigate("../path", { fromRouteId: "some-route" })`.
|
|
25
|
-
- This also applies to `router.fetch` which already receives a source route ID
|
|
26
|
-
|
|
27
|
-
- Introduce a new `@remix-run/router` `future.v7_prependBasename` flag to enable `basename` prefixing to all paths coming into `router.navigate` and `router.fetch`.
|
|
28
|
-
- Previously the `basename` was prepended in the React Router layer, but now that relative routing is being handled by the router we need prepend the `basename` _after_ resolving any relative paths
|
|
29
|
-
- This also enables `basename` support in `useFetcher` as well
|
|
7
|
+
- Enable `basename` support in `useFetcher` ([#10336](https://github.com/remix-run/react-router/pull/10336))
|
|
8
|
+
- 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')`)
|
|
30
9
|
|
|
31
10
|
### Patch Changes
|
|
32
11
|
|
|
33
12
|
- Fix inadvertent re-renders when using `Component` instead of `element` on a route definition ([#10287](https://github.com/remix-run/react-router/pull/10287))
|
|
34
13
|
- Fail gracefully on `<Link to="//">` and other invalid URL values ([#10367](https://github.com/remix-run/react-router/pull/10367))
|
|
35
|
-
- Switched from `useSyncExternalStore` to `useState` for internal `@remix-run/router` router state syncing in `<RouterProvider>`. 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://github.com/remix-run/react-router/pull/10377))
|
|
14
|
+
- Switched from `useSyncExternalStore` to `useState` for internal `@remix-run/router` router state syncing in `<RouterProvider>`. 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://github.com/remix-run/react-router/pull/10377), [#10409](https://github.com/remix-run/react-router/pull/10409))
|
|
15
|
+
- Add static prop to `StaticRouterProvider`'s internal `Router` component ([#10401](https://github.com/remix-run/react-router/pull/10401))
|
|
36
16
|
- 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://github.com/remix-run/react-router/pull/10336))
|
|
37
17
|
- Updated dependencies:
|
|
38
|
-
- `react-router@6.11.0
|
|
39
|
-
- `@remix-run/router@1.6.0
|
|
18
|
+
- `react-router@6.11.0`
|
|
19
|
+
- `@remix-run/router@1.6.0`
|
|
40
20
|
|
|
41
21
|
## 6.10.0
|
|
42
22
|
|
package/dist/index.js
CHANGED
package/dist/main.js
CHANGED
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "react-router-dom",
|
|
3
|
-
"version": "6.11.0
|
|
3
|
+
"version": "6.11.0",
|
|
4
4
|
"description": "Declarative routing for React web applications",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"react",
|
|
@@ -23,8 +23,8 @@
|
|
|
23
23
|
"module": "./dist/index.js",
|
|
24
24
|
"types": "./dist/index.d.ts",
|
|
25
25
|
"dependencies": {
|
|
26
|
-
"@remix-run/router": "1.6.0
|
|
27
|
-
"react-router": "6.11.0
|
|
26
|
+
"@remix-run/router": "1.6.0",
|
|
27
|
+
"react-router": "6.11.0"
|
|
28
28
|
},
|
|
29
29
|
"devDependencies": {
|
|
30
30
|
"react": "^18.2.0",
|