-
Notifications
You must be signed in to change notification settings - Fork 17
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
chore(deps): update dependency react-router-dom to v6 - autoclosed #110
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
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
from
November 10, 2021 00:19
f30f641
to
5713eba
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
from
November 20, 2021 05:05
5713eba
to
246c8d8
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
3 times, most recently
from
December 17, 2021 19:02
0e9ade1
to
bd59dcc
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
from
December 17, 2021 22:03
bd59dcc
to
75664ef
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
2 times, most recently
from
January 11, 2022 22:05
8eb8a51
to
4d389dd
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
2 times, most recently
from
March 1, 2022 02:13
589fe81
to
c2467a1
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
from
March 31, 2022 20:39
c2467a1
to
eadb875
Compare
renovate
bot
changed the title
chore(deps): update dependency react-router-dom to v6
chore(deps): update dependency react-router-dom to v6 - autoclosed
Apr 17, 2022
renovate
bot
changed the title
chore(deps): update dependency react-router-dom to v6 - autoclosed
chore(deps): update dependency react-router-dom to v6
Apr 17, 2022
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
8 times, most recently
from
February 27, 2023 21:49
a1a9e3b
to
3bb59fe
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
4 times, most recently
from
March 15, 2023 17:23
66b3406
to
9da6d68
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
5 times, most recently
from
March 29, 2023 20:17
085d838
to
0509fed
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
3 times, most recently
from
April 18, 2023 06:08
11f5f43
to
f9c199e
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
2 times, most recently
from
April 28, 2023 17:09
b451c1c
to
f0fcbf4
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
3 times, most recently
from
May 5, 2023 14:47
d2da5e1
to
0da4cb4
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
2 times, most recently
from
May 17, 2023 17:25
0f0fbc5
to
33cf7e5
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
3 times, most recently
from
May 29, 2023 06:06
48103c3
to
17cbd47
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
2 times, most recently
from
June 8, 2023 18:21
a7be46a
to
0a3fd8d
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
from
June 14, 2023 17:31
0a3fd8d
to
1cce098
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
3 times, most recently
from
June 30, 2023 20:37
9bbdecc
to
fc5ab13
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
from
July 17, 2023 22:46
fc5ab13
to
84f4aef
Compare
renovate
bot
force-pushed
the
renovate/major-react-router-monorepo
branch
from
July 25, 2023 12:49
84f4aef
to
56f771b
Compare
renovate
bot
changed the title
chore(deps): update dependency react-router-dom to v6
chore(deps): update dependency react-router-dom to v6 - autoclosed
Aug 9, 2023
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:
5.3.4
->6.14.2
Release Notes
remix-run/react-router (react-router-dom)
v6.14.2
Compare Source
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
v6.4.5
Compare Source
Patch Changes
@remix-run/router@1.0.5
react-router@6.4.5
v6.4.4
Compare Source
Patch Changes
NavLink
and descendant<Routes>
(#9589, #9647)ErrorResponse
instances when using built-in hydration (#9593)basename
in static data routers (#9591)@remix-run/router@1.0.4
react-router@6.4.4
v6.4.3
Compare Source
Patch Changes
createHashRouter
(#9409)index
routes with apath
inuseResolvedPath
(#9486)relative=path
prop onNavLink
(#9453)NavLink
behavior for root urls (#9497)@remix-run/router@1.0.3
react-router@6.4.3
v6.4.2
Compare Source
Patch Changes
basename
inuseFormAction
(#9352)RouteObject
/RouteProps
types to surface the error in TypeScript. (#9366)react-router@6.4.2
@remix-run/router@1.0.2
v6.4.1
Compare Source
Patch Changes
react-router@6.4.1
@remix-run/router@1.0.1
v6.4.0
Compare Source
Whoa this is a big one!
6.4.0
brings all the data loading and mutation APIs over from Remix. Here's a quick high level overview, but it's recommended you go check out the docs, especially the feature overview and the tutorial.New APIs
createMemoryRouter
/createBrowserRouter
/createHashRouter
<RouterProvider>
loader
and mutate with a Routeaction
errorElement
<Form>
componentuseFetcher()
defer
andAwait
<ScrollRestoration>
New Features
<Link relative="path">
(#9160)Bug Fixes
useLocation
returns the scoped location inside a<Routes location>
component (#9094)<Link replace>
prop if it is defined (#8779)Updated Dependencies
react-router@6.4.0
v6.3.0
: react-router@v6.3.0Compare Source
What's Changed
New Contributors
Full Changelog: remix-run/react-router@v6.2.2...v6.3.0
v6.2.2
Compare Source
What's Changed
🐛 Bug Fixes
New Contributors
Full Changelog: remix-run/react-router@v6.2.1...v6.2.2
v6.2.1
Compare Source
This release updates the internal
history
dependency to5.2.0
.Full Changelog: remix-run/react-router@v6.2.0...v6.2.1
v6.2.0
Compare Source
🐛 Bug fixes
RouteProps
element
type, which should be aReactNode
(#8473)useOutlet
for top-level routes (#8483)✨ Features
New Contributors
Full Changelog: remix-run/react-router@v6.1.1...v6.2.0
v6.1.1
Compare Source
In v6.1.0 we inadvertently shipped a new, undocumented API that will likely introduce bugs (#7586). We have flagged
HistoryRouter
asunstable_HistoryRouter
, as this API will likely need to change before a new major release.Full Changelog: remix-run/react-router@v6.1.0...v6.1.1
v6.1.0
Compare Source
🐛 Bug fixes
✨ Features
<Outlet>
can now receive acontext
prop. This value is passed to child routes and is accessible via the newuseOutletContext
hook. See the API docs for details. (#8461)<NavLink>
can now receive a child function for access to its props. (#8164)💅 Enhancements
useMatch
andmatchPath
. For example, when you calluseMatch("foo/:bar/:baz")
, the path is parsed and the return type will bePathMatch<"bar" | "baz">
. (#8030)New Contributors
Full Changelog: remix-run/react-router@v6.0.1...v6.1.0
v6.0.2
Compare Source
✨ Features
reloadDocument
prop to<Link>
. This allows<Link>
to function like a normal anchor tag by reloading the document after navigation while maintaining the relativeto
resolution.🗒️ Docs
🤝 New Contributors
Full Changelog
v6.0.1
Compare Source
🐛 Bug Fixes
<StaticRouter location>
value (#8243)<Route>
inside<Routes>
to help people make the change (#8238)v6.0.0
Compare Source
React Router v6 is here!
Please go read our blog post for more information on all the great stuff in v6 including notes about how to upgrade from React Router v5 and Reach Router.
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" in timezone America/New_York, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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.