[Snyk] Upgrade history from 5.0.0 to 5.0.1 #101
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
It might be the setting causing issues with Django / pgBouncer leading to 500 errors when db connection is dropped
Snyk has created this PR to upgrade history from 5.0.0 to 5.0.1. See this package in npm: https://www.npmjs.com/package/history See this project in Snyk: https://app.snyk.io/org/rriski/project/599b05f1-0aa8-44ca-899b-23cf5457cfe8?utm_source=github&utm_medium=upgrade-pr
Codecov Report
@@ Coverage Diff @@
## master #101 +/- ##
=======================================
Coverage 62.61% 62.61%
=======================================
Files 132 132
Lines 4917 4917
=======================================
Hits 3079 3079
Misses 1838 1838
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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 5.0.0 to 5.0.1.
ℹ️ 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.
Release notes
Package name: history
-
5.0.1 - 2021-08-13
-
5.0.0 - 2020-06-12
- Hash history now has support for
- Better
- Full TypeScript declarations and IntelliSense docs
- Adds development and production builds for
- Both browser and hash history have support for iframes (custom
- About 50% smaller than v4 (and no dependencies)
- Fixed some long-standing encoding issues with
- Removed unfixable warnings about pushing the same path in hash history
- Renamed browser global to
- Removed support for browsers that do not support the HTML5 history API (no
- Removed relative pathname support in hash history and memory history
- Removed
from history GitHub release notesThis patch release contains a tiny TypeScript update to use the built-in
Partialutility forPartialPathandPartialLocation. 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.statehistory.blockAPI, with support for retrying transitions<script type=module>userswindowobjects)Bugfixes
location.pathnameHistoryLibraryso it doesn't conflict withwindow.HistoryBreaking Changes
pushState)getUserConfirmation,keyLength, andhashTypeAPIsUsage
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
docsfolder.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! 😀
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