Skip to content

refactor: upgrade history from 4.10.1 to 5.3.0 #2072

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 8 commits into from

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade history from 4.10.1 to 5.3.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.

  • The recommended version is 18 versions ahead of your current version.
  • The recommended version was released a month ago, on 2022-02-22.
Release notes
Package name: history
  • 5.3.0 - 2022-02-22

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

  • 5.3.0-pre.0 - 2022-02-18
    No content.
  • 5.2.0 - 2021-12-17

    🐛 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: v5.1.0...v5.2.0

  • 5.1.0 - 2021-11-02

    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: v5.0.3...v5.1.0

  • 5.0.3 - 2021-11-01

    Fixed parsePath adding incorrectly adding search

  • 5.0.2 - 2021-11-01

    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: v5.0.1...v5.0.2

  • 5.0.1 - 2021-08-13

    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!

  • 5.0.0 - 2020-06-12

    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! 😀

  • 5.0.0-beta.9 - 2020-04-29

    Version 5.0.0-beta.9

  • 5.0.0-beta.8 - 2020-04-17

    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!

  • 5.0.0-beta.7 - 2020-03-26
  • 5.0.0-beta.6 - 2020-03-26
  • 5.0.0-beta.5 - 2020-02-07
  • 5.0.0-beta.4 - 2020-01-22
  • 5.0.0-beta.3 - 2019-12-11
  • 5.0.0-beta.2 - 2019-12-07
  • 5.0.0-beta.1 - 2019-12-03
  • 5.0.0-beta.0 - 2019-11-08
  • 4.10.1 - 2019-09-13
from history GitHub release notes
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

@parse-github-assistant
Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title [Snyk] Upgrade history from 4.10.1 to 5.3.0 refactor: upgrade history from 4.10.1 to 5.3.0 Mar 25, 2022
@mtrezza
Copy link
Member

mtrezza commented Apr 3, 2022

Closing, outdated

@mtrezza mtrezza deleted the snyk-upgrade-f6d22f98c6a14416a31afa8f0014305a branch April 3, 2022 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants