fix(deps): update dependency history to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
history	4.10.1 -> 5.0.1

---

Release Notes

ReactTraining/history

v5.0.1

Compare Source

This patch release contains a tiny TypeScript update to use the built-in Partial utility for PartialPath and PartialLocation. We always love it when we can ship just a little less code!

🙏 Credits

Thanks to @​liuhanqu, @​hanquliu, @​chaance and @​mjackson for your contributions!

v5.0.0

Compare Source

Today we are very pleased to announce the stable release of history version 5!

Overview

This version includes many enhancements and fixes a few important issues with the library.

New Features

• Hash history now has support for location.state
• Better history.block API, with support for retrying transitions
• Full TypeScript declarations and IntelliSense docs
• Adds development and production builds for <script type=module> users
• Both browser and hash history have support for iframes (custom window objects)
• About 50% smaller than v4 (and no dependencies)

Bugfixes

• Fixed some long-standing encoding issues with location.pathname
• Removed unfixable warnings about pushing the same path in hash history
• Renamed browser global to HistoryLibrary so it doesn't conflict with window.History

Breaking Changes

• Removed support for browsers that do not support the HTML5 history API (no pushState)
• Removed relative pathname support in hash history and memory history
• Removed getUserConfirmation, keyLength, and hashType APIs

Usage

Please refer to our installation guide for instructions about how to install the library.

There is also a getting started guide as well as a complete API reference in the docs folder.

We are very excited about this release, especially because it will serve as the foundation for the upcoming release of React Router version 6.

Thank you for your support. Enjoy! 😀

---

Configuration

📅 Schedule: 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.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[edalex-ian]

To support this some manual code updates are needed:

Error: Source/Plugins/Core/com.equella.core/js/tsrc/mainui/LegacyPage.tsx(26,20): error TS2305: Module '"../../node_modules/history"' has no exported member 'LocationDescriptor'.
Error: Source/Plugins/Core/com.equella.core/js/tsrc/mainui/Template.tsx(49,10): error TS2305: Module '"../../node_modules/history"' has no exported member 'LocationDescriptor'.
Error: Source/Plugins/Core/com.equella.core/js/tsrc/mainui/routes.tsx(20,15): error TS2305: Module '"../../node_modules/history"' has no exported member 'LocationDescriptor'.
Error: Source/Plugins/Core/com.equella.core/js/tsrc/search/SearchPage.tsx(152,7): error TS2345: Argument of type '{ state: { searchPageOptions: SearchPageOptions; filterExpansion: boolean; }; key: string; pathname: string; search: string; hash: string; }' is not assignable to parameter of type 'To'.
  Object literal may only specify known properties, and 'state' does not exist in type 'PartialPath'.

[edalex-ian]

Seems like the 5.0.x release is causing a bit of pain for a lot of the community and most are currently avoiding upgrading. See:

• Upgrading from 4.10.1 to 5.0.0: history/index"' has no exported member 'LocationDescriptor'. remix-run/history#846
• [v5] Undocumented breaking changes remix-run/history#811

Closing for now, hopefully things improve in the future.

[renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 5.x releases. However, if you upgrade to 5.x manually then Renovate will reenable minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.