refactor: Upgrade path-to-regexp from 0.1.7 to 6.2.1

[snyk-bot]

Snyk has created this PR to upgrade path-to-regexp from 0.1.7 to 6.2.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.

---

Warning: This is a major version upgrade, and may be a breaking change.

• The recommended version is 43 versions ahead of your current version.
• The recommended version was released a year ago, on 2022-05-06.

Release notes

Package name: path-to-regexp

• 6.2.1 - 2022-05-06
  

  Fixed

  • Fix invalid matching of :name* parameter (#261) 762bc6b
  • Compare delimiter string over regexp 86baef8

  Added

  • New example in documentation (#256) ae9e576
  • Update demo link (#250) 77df638
  • Update README encode example b39edd4

  v6.2.0...v6.2.1

• 6.2.0 - 2020-09-29
  

  Added

  • Support named capturing groups for RegExps (#225)

  Fixed

  • Update strict flag documentation (#227)
  • Ignore test files when bundling (#220)
• 6.1.0 - 2019-11-20
  

  Fixed

  • Use /#? as default delimiter to avoid matching on query or fragment parameters
    • If you are matching non-paths (e.g. hostnames), you can adjust delimiter: '.'
• 6.0.0 - 2019-11-20
  

  Note: The path syntax has been stabilized with this release, no breaking changes in paths is expected.

  This release reverts the prefix behavior added in v3 back to the behavior seen in v2. For the most part, path matching is backward compatible with v2 with these enhancements:

  1. Support for nested non-capturing groups in regexp, e.g. /(abc(?=d))
  2. Support for custom prefix and suffix groups using /{abc(.*)def}
  3. Tokens in an unexpected position will throw an error
     • Paths like /test(foo previously worked treating ( as a literal character, now it expects ( to be closed and is treated as a group
     • You can escape the character for the previous behavior, e.g. /test\(foo

  Changed

  • Revert using any character as prefix, support prefixes option to configure this (starts as /. which acts like every version since 0.x again)
  • Add support for {} to capture prefix/suffix explicitly, enables custom use-cases like /:attr1{-:attr2}?
• 5.0.0 - 2019-11-12
  

  No changes to path rules since 3.x, except support for nested RegEx parts in 4.x.

  Changed

  • Rename RegexpOptions interface to TokensToRegexpOptions
  • Remove normalizePathname from library, document solution in README
  • Encode using identity function as default, not encodeURIComponent
• 4.0.5 - 2019-11-12
  

  Removed

  • Remove whitelist in favor of decodeURI (advanced behavior can happen outside path-to-regexp)
• 4.0.4 - 2019-11-12
  

  Fixed

  • Remove usage of String.prototype.normalize to continue supporting IE
• 4.0.3 - 2019-11-12
  

  Added

  • Add normalize whitelist of characters (defaults to /%.-)
• 4.0.2 - 2019-11-12
  

  Fixed

  • Allow RegexpOptions in match(...) function
• 4.0.1 - 2019-11-12
  

  Fixed

  • Normalize regexp spelling across 4.x
• 4.0.0 - 2019-11-12
• 3.2.0 - 2019-11-11
• 3.1.0 - 2019-08-31
• 3.0.0 - 2019-01-14
• 2.4.0 - 2018-08-26
• 2.3.0 - 2018-08-20
• 2.2.1 - 2018-04-24
• 2.2.0 - 2018-03-07
• 2.1.0 - 2017-10-20
• 2.0.0 - 2017-08-23
• 1.8.0 - 2019-11-11
• 1.7.0 - 2016-11-08
• 1.6.0 - 2016-10-03
• 1.5.3 - 2016-06-16
• 1.5.2 - 2016-06-16
• 1.5.1 - 2016-06-08
• 1.5.0 - 2016-05-20
• 1.4.0 - 2016-05-19
• 1.3.0 - 2016-05-08
• 1.2.1 - 2015-08-17
• 1.2.0 - 2015-05-21
• 1.1.1 - 2015-05-12
• 1.1.0 - 2015-05-09
• 1.0.3 - 2015-01-17
• 1.0.2 - 2014-12-17
• 1.0.1 - 2014-08-28
• 1.0.0 - 2014-08-17
• 0.2.5 - 2014-08-07
• 0.2.4 - 2014-08-02
• 0.2.3 - 2014-07-08
• 0.2.2 - 2014-07-06
• 0.2.1 - 2014-06-11
• 0.2.0 - 2014-06-10
• 0.1.7 - 2015-07-28

from path-to-regexp GitHub release notes

Commit messages

Package name: path-to-regexp

• b0778f5 6.2.1
• 446abfb Remove tslint comments
• 86baef8 Compare delimiter string over regexp
• 762bc6b Fix invalid matching of `:name*` parameter (Request timeout with a Cloud Function that returns large JSON payload #261)
• b45871b Reformat repo, upgrade build, use github actions
• ae9e576 New example in documentation (Schemas endpoint: ignore '_metadata' key, convert 'map' type to Object #256)
• 77df638 Update demo link (Use Mailgun as default implementation for reset password and email verification. #250)
• b39edd4 Update README encode example
• 125c43e 6.2.0
• e1c39ed Remove `git add` from commit hook
• c8f78d8 Test using TypeScript v4
• d8bc41f Run tests on min node.js v10
• 3bc24b2 Upgrade dev dependencies
• feddb3d Support named capturing groups for RegExps (Adds standalone parse server #225)
• 8b0ae94 Fix `after_script` with push to coveralls
• 89008cb Update `strict` flag documentation (Add GCM client #227)
• 98ab888 Update example RegExp (Adding validation functions to Cloud Functions #224)
• 0c466b1 Ignore test files when bundling (Schema mismatch for _Session.expiresAt #220)
• 7b4078d Add modifier suffix example using new `{}` syntax
• d830155 Add link for history notes moving to releases
• 4b8efcc 6.1.0
• 55702b2 Update README examples using token `delimiter`
• 43e87bf Document query string behavior (updated regexr link for updated regex #210)
• 2ea948c Use `/#?` as default delimiter

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]

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

[parseplatformorg]

🎉 This change has been released in version 6.1.0-alpha.13

[parseplatformorg]

🎉 This change has been released in version 6.3.0-beta.1

[parseplatformorg]

🎉 This change has been released in version 6.3.0-alpha.1

[parseplatformorg]

🎉 This change has been released in version 6.3.0