Skip to content

Upgrade react-router-dom to version 6.11.0#126

Closed
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/ApplicationCodeMyprojectfrontend/npm/react-router-dom-6.11.0
Closed

Upgrade react-router-dom to version 6.11.0#126
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/ApplicationCodeMyprojectfrontend/npm/react-router-dom-6.11.0

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Apr 29, 2023

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ react-router-dom (^5.2.0 → ^6.11.0) · Repo · Changelog

Release Notes

6.11.0 (from changelog)

Minor Changes

  • Enable basename support in useFetcher (#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)
  • Fail gracefully on <Link to="//"> and other invalid URL values (#10367)
  • Switched from useSyncExternalStore to useState for internal @remix-run/router router state syncing in <RouterProvider>. We found some subtle bugs where router state updates got propagated before other normal useState updates, which could lead to footguns in useEffect calls. (#10377, #10409)
  • Add static prop to StaticRouterProvider's internal Router component (#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)
  • Updated dependencies:
    • react-router@6.11.0
    • @remix-run/router@1.6.0

Does any of this look wrong? Please let us know.


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu
Copy link
Contributor Author

depfu bot commented May 4, 2023

Closed in favor of #127.

@depfu depfu bot closed this May 4, 2023
@depfu depfu bot deleted the depfu/update/ApplicationCodeMyprojectfrontend/npm/react-router-dom-6.11.0 branch May 4, 2023 23:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants