[Snyk] Upgrade path-to-regexp from 0.1.7 to 6.2.0 #2
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 path-to-regexp from 0.1.7 to 6.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: path-to-regexp
-
6.2.0 - 2020-09-29
- Support named capturing groups for RegExps (#225)
- Update
- Ignore test files when bundling (#220)
-
6.1.0 - 2019-11-20
- Use
- If you are matching non-paths (e.g. hostnames), you can adjust
-
6.0.0 - 2019-11-20
- Support for nested non-capturing groups in regexp, e.g.
- Support for custom prefix and suffix groups using
- Tokens in an unexpected position will throw an error
- Things like
- You can escape the character for the previous behavior, e.g.
- Revert using any character as prefix, support
- Add support for
-
5.0.0 - 2019-11-12
- Rename
- Remove
- Encode using identity function as default, not
-
4.0.5 - 2019-11-12
- Remove
-
4.0.4 - 2019-11-12
- Remove usage of
-
4.0.3 - 2019-11-12
- Add normalize whitelist of characters (defaults to
-
4.0.2 - 2019-11-12
- Allow
-
4.0.1 - 2019-11-12
- Normalize
-
4.0.0 - 2019-11-12
- Export names have changed to support ES2015 modules in bundlers
- New
- Support nested non-capturing groups within parameters
- Add tree-shaking (via ES2015 modules) for webpack and other bundlers
-
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 notesAdded
Fixed
strictflag documentation (#227)Fixed
/#?as default delimiter to avoid matching on query or fragment parametersdelimiter: '.'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:
/(abc(?=d))/{abc(.*)def}/test(foopreviously would worked, now it expects(to be closed/test\(fooChanged
prefixesoption to configure this (starts as/.which acts like every version since 0.x again){}to capture prefix/suffix explicitly, enables custom use-cases like/:attr1{-:attr2}?No changes to path rules since 3.x, except support for nested RegEx parts in 4.x.
Changed
RegexpOptionsinterface toTokensToRegexpOptionsnormalizePathnamefrom library, document solution in READMEencodeURIComponentRemoved
whitelistin favor ofdecodeURI(advanced behavior can happen outsidepath-to-regexp)Fixed
String.prototype.normalizeto continue supporting IEAdded
/%.-)Fixed
RegexpOptionsinmatch(...)functionFixed
regexpspelling across 4.xAll path rules are backward compatible with 3.x, except for nested
()and other RegEx special characters that were previously ignored.Changed
matchdoes not default todecodeURIComponentAdded
normalizePathnameutility for supporting unicode paths in librariesCommit messages
Package name: path-to-regexp
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