[Snyk] Upgrade history from 1.17.0 to 5.2.0 #9
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.
Snyk has created this PR to upgrade history from 1.17.0 to 5.2.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Warning: This is a major version upgrade, and may be a breaking change.
Release notes
Package name: history
🐛 Bug fixes
State
(now set tounknown
which will require consumer type narrowing)PartialPath
(usePartial<Path>
instead)PartialLocation
(usePartial<Location>
instead)createPath
return value (#813)✨ Features
Full Changelog: v5.1.0...v5.2.0
Because the prior 5.0.2 release removed the
State
type parameter fromLocation
, 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: v5.0.3...v5.1.0
Fixed
parsePath
adding incorrectly addingsearch
Just a couple fixes:
location.state
type toany
and removed the generic onLocation
Full Changelog: v5.0.1...v5.0.2
This patch release contains a tiny TypeScript update to use the built-in
Partial
utility forPartialPath
andPartialLocation
. We always love it when we can ship just a little less code!🙏 Credits
Thanks to @ liuhanqu, @ hanquliu, @ chaance and @ mjackson for your contributions!
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
location.state
history.block
API, with support for retrying transitions<script type=module>
userswindow
objects)Bugfixes
location.pathname
HistoryLibrary
so it doesn't conflict withwindow.History
Breaking Changes
pushState
)getUserConfirmation
,keyLength
, andhashType
APIsUsage
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! 😀
Version 5.0.0-beta.9
You can track v5 beta progress in #751
You can install the v5 beta using the
next
tag:npm add history@next
Changes
In this release the core library was converted to TypeScript, and the type declaration files that are published with the npm package are derived from the source instead of being written by hand. This should make them both more accurate and more useful.
A migration guide will be available soon. For now, you can either browse around the docs on the
dev
branch or the tests.Enjoy!
Version 5.0.0-beta.7
Version 5.0.0-beta.6
Commit messages
Package name: history
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs