-
-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update dependency react-router-dom to ~6.16.0 - autoclosed #938
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
642d204
to
ad8cf2e
Compare
ad8cf2e
to
d53972b
Compare
d53972b
to
14d9477
Compare
14d9477
to
a8fcff7
Compare
6e90367
to
b3523f1
Compare
b3523f1
to
6acc118
Compare
6acc118
to
71467dd
Compare
4c7ac82
to
1235e2b
Compare
543f46e
to
1ae3542
Compare
1ae3542
to
fc5d522
Compare
fc5d522
to
c2491e1
Compare
c2491e1
to
565b14b
Compare
565b14b
to
2d8ed59
Compare
2d8ed59
to
56d2ef6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
~6.4.2
->~6.16.0
Release Notes
remix-run/react-router (react-router-dom)
v6.16.0
Compare Source
Minor Changes
@remix-run/router@1.9.0
react-router@6.16.0
Patch Changes
v6.15.0
Compare Source
Minor Changes
redirectDocument()
function which allows users to specify that a redirect from aloader
/action
should trigger a document reload (viawindow.location
) instead of attempting to navigate to the redirected location via React Router (#10705)Patch Changes
URLSearchParams
and theuseSearchParams
hook. (#10620)useFormAction()
for unspecified actions since it cannot be determined on the server and causes hydration issues (#10758)unstable_usePrompt
to avoid throwing an exception if the prompt is unblocked and a navigation is performed synchronously (#10687, #10718)@remix-run/router@1.8.0
react-router@6.15.0
v6.14.2
Compare Source
Patch Changes
<ScrollRestoration>
(#10682)<Form state>
prop to populatehistory.state
on submission navigations (#10630)Error
subclasses such asReferenceError
/TypeError
(#10633)@remix-run/router@1.7.2
react-router@6.14.2
v6.14.1
Compare Source
Patch Changes
react-router@6.14.1
@remix-run/router@1.7.1
v6.14.0
Compare Source
Minor Changes
Add support for
application/json
andtext/plain
encodings foruseSubmit
/fetcher.submit
. To reflect these additional types,useNavigation
/useFetcher
now also containnavigation.json
/navigation.text
andfetcher.json
/fetcher.text
which include the json/text submission if applicable (#10413)Patch Changes
submitter
element, prefer the built-innew FormData(form, submitter)
instead of the previous manual approach in modern browsers (those that support the newsubmitter
parameter) (#9865, #10627)type="image"
buttonsformdata-submitter-polyfill
window.history.pushState/replaceState
before updating React Router state (instead of after) so thatwindow.location
matchesuseLocation
during synchronous React 17 rendering (#10448)window.location
and should always referenceuseLocation
when possible, aswindow.location
will not be in sync 100% of the time (due topopstate
events, concurrent mode, etc.)tsc --skipLibCheck:false
issues on React 17 (#10622)typescript
to 5.1 (#10581)react-router@6.14.0
@remix-run/router@1.7.0
v6.13.0
Compare Source
Minor Changes
Move
React.startTransition
usage behind a future flag to avoid issues with existing incompatibleSuspense
usages. We recommend folks adopting this flag to be better compatible with React concurrent mode, but if you run into issues you can continue without the use ofstartTransition
until v7. Issues usually boils down to creating net-new promises during the render cycle, so if you run into issues you should either lift your promise creation out of the render cycle or put it behind auseMemo
. (#10596)Existing behavior will no longer include
React.startTransition
:If you wish to enable
React.startTransition
, pass the future flag to your component:Patch Changes
React.startTransition
minification bug in production mode (#10588)react-router@6.13.0
v6.12.1
Compare Source
Patch Changes
React.startTransition
to fix webpack + react 17 compilation error (#10569)react-router@6.12.1
v6.12.0
Compare Source
Minor Changes
React.startTransition
if it exists (#10438)Patch Changes
DOMException
(DataCloneError
) when attempting to perform aPUSH
navigation with non-serializable state. (#10427)@remix-run/router@1.6.3
react-router@6.12.0
v6.11.2
Compare Source
Patch Changes
SetURLSearchParams
type (#10444)react-router@6.11.2
@remix-run/router@1.6.2
v6.11.1
Compare Source
Patch Changes
react-router@6.11.1
@remix-run/router@1.6.1
v6.11.0
Compare Source
Minor Changes
basename
support inuseFetcher
(#10336)basename
then you will need to remove the manually prependedbasename
from yourfetcher
calls (fetcher.load('/basename/route') -> fetcher.load('/route')
)Patch Changes
Component
instead ofelement
on a route definition (#10287)<Link to="//">
and other invalid URL values (#10367)useSyncExternalStore
touseState
for internal@remix-run/router
router state syncing in<RouterProvider>
. We found some subtle bugs where router state updates got propagated before other normaluseState
updates, which could lead to footguns inuseEffect
calls. (#10377, #10409)StaticRouterProvider
's internalRouter
component (#10401)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 onuseLocation()
. When usingBrowserRouter
, these hooks remain unstable across location changes because they still rely onuseLocation()
. (#10336)react-router@6.11.0
@remix-run/router@1.6.0
v6.10.0
Compare Source
Minor Changes
Added support for Future Flags in React Router. The first flag being introduced is
future.v7_normalizeFormMethod
which will normalize the exposeduseNavigation()/useFetcher()
formMethod
fields as uppercase HTTP methods to align with thefetch()
behavior. (#10207)future.v7_normalizeFormMethod === false
(default v6 behavior),useNavigation().formMethod
is lowercaseuseFetcher().formMethod
is lowercasefuture.v7_normalizeFormMethod === true
:useNavigation().formMethod
is uppercaseuseFetcher().formMethod
is uppercasePatch Changes
createStaticHandler
to also check forErrorBoundary
on routes in addition toerrorElement
(#10190)@remix-run/router@1.5.0
react-router@6.10.0
v6.9.0
Compare Source
Minor Changes
React Router now supports an alternative way to define your route
element
anderrorElement
fields as React Components instead of React Elements. You can instead pass a React Component to the newComponent
andErrorBoundary
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 doComponent
/ErrorBoundary
will "win". (#10045)Example JSON Syntax
Example JSX Syntax
Introducing Lazy Route Modules! (#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
orsubmitting
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.Then in your lazy route modules, export the properties you want defined for the route:
An example of this in action can be found in the
examples/lazy-loading-router-provider
directory of the repository.🙌 Huge thanks to @rossipedia for the Initial Proposal and POC Implementation.
Updated dependencies:
react-router@6.9.0
@remix-run/router@1.4.0
v6.8.2
Compare Source
Patch Changes
<Link to>
as external if they are outside of the routerbasename
(#10135)useBlocker
to returnIDLE_BLOCKER
during SSR (#10046)<Link to>
urls (#10112)StaticRouterProvider
serialized hydration data (#10068)@remix-run/router@1.3.3
react-router@6.8.2
v6.8.1
Compare Source
Patch Changes
Link
component (now also supportsmailto:
urls) (#9994)react-router@6.8.1
@remix-run/router@1.3.2
v6.8.0
Compare Source
Minor Changes
Support absolute URLs in
<Link to>
. If the URL is for the current origin, it will still do a client-side navigation. If the URL is for a different origin then it will do a fresh document request for the new origin. (#9900)Patch Changes
useSearchParams
(#9969)preventScrollReset
on<fetcher.Form>
(#9963)pagehide
instead ofbeforeunload
for<ScrollRestoration>
. This has better cross-browser support, specifically on Mobile Safari. (#9945)@remix-run/router@1.3.1
react-router@6.8.0
v6.7.0
Compare Source
Minor Changes
unstable_useBlocker
hook for blocking navigations within the app's location origin (#9709)unstable_usePrompt
hook for blocking navigations within the app's location origin (#9932)preventScrollReset
prop to<Form>
(#9886)Patch Changes
useBeforeUnload
(#9709)@remix-run/router@1.3.0
react-router@6.7.0
v6.6.2
Compare Source
Patch Changes
useId
consistency during SSR (#9805)react-router@6.6.2
v6.6.1
Compare Source
Patch Changes
@remix-run/router@1.2.1
react-router@6.6.1
v6.6.0
Compare Source
Minor Changes
useBeforeUnload()
hook (#9664)unstable_
prefix fromcreateStaticHandler
/createStaticRouter
/StaticRouterProvider
(#9738)Patch Changes
Error
objects fromStaticRouterProvider
(#9664)<Form method>
anduseSubmit
method values (#9664)hydrationData
(#9664)<button formmethod>
form submission overriddes (#9664)@remix-run/router@1.2.0
react-router@6.6.0
v6.5.0
Compare Source
Patch Changes
react-router@6.5.0
@remix-run/router@1.1.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.