react-router-dom-v5-compat 6.21.0-pre.0 → 6.21.0-pre.2

package/CHANGELOG.md

@@ -1,12 +1,28 @@
 # `react-router-dom-v5-compat`
 
+## 6.21.0-pre.2
+
+### Patch Changes
+
+- Updated dependencies:
+  - `react-router-dom@6.21.0-pre.2`
+  - `react-router@6.21.0-pre.2`
+
+## 6.21.0-pre.1
+
+### Patch Changes
+
+- Updated dependencies:
+  - `react-router-dom@6.21.0-pre.1`
+  - `react-router@6.21.0-pre.1`
+
 ## 6.21.0-pre.0
 
 ### Minor Changes
 
-- Add a new `future.v7_relativeSplatPath` flag to implenent a breaking bug fix to relative routing when inside a splat route. ([#11087](https://github.com/remix-run/react-router/pull/11087))
+- Add a new `future.v7_relativeSplatPath` flag to implement a breaking bug fix to relative routing when inside a splat route. ([#11087](https://github.com/remix-run/react-router/pull/11087))
 
-  This fix was originally added in [#10983](https://github.com/remix-run/react-router/issues/10983) and was later reverted in [#11078](https://github.com/remix-run/react-router/issues/110788) because it was determined that a large number of existing applications were relying on the buggy behavior (see [#11052](https://github.com/remix-run/react-router/issues/11052))
+  This fix was originally added in [#10983](https://github.com/remix-run/react-router/issues/10983) and was later reverted in [#11078](https://github.com/remix-run/react-router/pull/11078) because it was determined that a large number of existing applications were relying on the buggy behavior (see [#11052](https://github.com/remix-run/react-router/issues/11052))
 
   **The Bug**
   The buggy behavior is that without this flag, the default behavior when resolving relative paths is to _ignore_ any splat (`*`) portion of the current route path.
@@ -50,7 +66,7 @@
 
   **The Problem**
 
-  The problem is that this concept of ignoring part of a pth breaks a lot of other assumptions in React Router - namely that `"."` always means the current location pathname for that route. When we ignore the splat portion, we start getting invalid paths when using `"."`:
+  The problem is that this concept of ignoring part of a path breaks a lot of other assumptions in React Router - namely that `"."` always means the current location pathname for that route. When we ignore the splat portion, we start getting invalid paths when using `"."`:
 
   ```jsx
   // If we are on URL /dashboard/team, and we want to link to /dashboard/team:

package/dist/index.js

@@ -1,5 +1,5 @@
 /**
- * React Router DOM v5 Compat v6.21.0-pre.0
+ * React Router DOM v5 Compat v6.21.0-pre.2
  *
  * Copyright (c) Remix Software Inc.
  *
@@ -549,10 +549,7 @@ function RouterProvider(_ref) {
     router,
     navigator,
     static: false,
-    basename,
-    future: {
-      v7_relativeSplatPath: router.future.v7_relativeSplatPath
-    }
+    basename
   }), [router, navigator, basename]);
   // The fragment and {null} here are important!  We need them to keep React 18's
   // useId happy when we are server-rendering since we may have a <script> here
@@ -572,7 +569,10 @@ function RouterProvider(_ref) {
     basename: basename,
     location: state.location,
     navigationType: state.historyAction,
-    navigator: navigator
+    navigator: navigator,
+    future: {
+      v7_relativeSplatPath: router.future.v7_relativeSplatPath
+    }
   }, state.initialized ? /*#__PURE__*/React.createElement(DataRoutes, {
     routes: router.routes,
     future: router.future,