Update dependency history to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
history	^4.10.1 -> ^5.3.0

---

Release Notes

remix-run/history (history)

v5.3.0

Compare Source

This release provides support for native ESM consumption of all exports.

v5.2.0

Compare Source

🐛 Bug fixes

• Fixed a few type declarations and deprecated the following types:
  • State (now set to unknown which will require consumer type narrowing)
  • PartialPath (use Partial<Path> instead)
  • PartialLocation (use Partial<Location> instead)
• Fixed a regression related to the createPath return value (#​813)

✨ Features

• We now use statically analyzable CJS exports. This enables named imports in Node ESM scripts (See the commit).

Full Changelog: remix-run/history@v5.1.0...v5.2.0

v5.1.0

Compare Source

Because the prior 5.0.2 release removed the State type parameter from Location, this was technically a breaking change. To correct for this, I'm bumping this as a minor release. It won't affect runtime code, but it may affect your development experience and tests if you were using that parameter.

The State type export is also restored, so you shouldn't have issues with installing React Router v6.

Oh, by the way, did you hear we released React Router v6?

Full Changelog: remix-run/history@v5.0.3...v5.1.0

v5.0.3

Compare Source

Fixed parsePath adding incorrectly adding search

v5.0.2

Compare Source

Just a couple fixes:

• Fixed search params persisting on redirects
• Changed the location.state type to any and removed the generic on Location

Full Changelog: remix-run/history@v5.0.1...v5.0.2

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

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: admin/package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @comet/[email protected]
npm error Found: [email protected]
npm error node_modules/history
npm error   history@"^5.3.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer history@"^4.10.1" from @comet/[email protected]
npm error node_modules/@comet/admin
npm error   @comet/admin@"^7.11.0" from the root project
npm error   @comet/admin@"^7.11.0" from @comet/[email protected]
npm error   node_modules/@comet/admin-date-time
npm error     @comet/admin-date-time@"^7.11.0" from @comet/[email protected]
npm error     node_modules/@comet/cms-admin
npm error       @comet/cms-admin@"^7.11.0" from the root project
npm error   3 more (@comet/admin-rte, @comet/blocks-admin, @comet/cms-admin)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/history
npm error   peer history@"^4.10.1" from @comet/[email protected]
npm error   node_modules/@comet/admin
npm error     @comet/admin@"^7.11.0" from the root project
npm error     @comet/admin@"^7.11.0" from @comet/[email protected]
npm error     node_modules/@comet/admin-date-time
npm error       @comet/admin-date-time@"^7.11.0" from @comet/[email protected]
npm error       node_modules/@comet/cms-admin
npm error         @comet/cms-admin@"^7.11.0" from the root project
npm error     3 more (@comet/admin-rte, @comet/blocks-admin, @comet/cms-admin)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-01-14T13_37_07_232Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-14T13_37_07_232Z-debug-0.log

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud