fix(deps): update dependency path-to-regexp to v6 - abandoned #60
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.
This PR contains the following updates:
^3.2.0
->^6.0.0
Release Notes
pillarjs/path-to-regexp
v6.2.1
: Fix matching:name*
parameterCompare Source
Fixed
:name*
parameter (#261)762bc6b
86baef8
Added
ae9e576
77df638
b39edd4
v6.2.0
: Named Capturing GroupsCompare Source
Added
Fixed
strict
flag documentation (#227)v6.1.0
: Use `/#?` as Default DelimiterCompare Source
Fixed
/#?
as default delimiter to avoid matching on query or fragment parametersdelimiter: '.'
v6.0.0
: Custom Prefix and Suffix GroupsCompare Source
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(foo
previously worked treating(
as a literal character, now it expects(
to be closed and is treated as a group/test\(foo
Changed
prefixes
option 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}?
v5.0.0
: Remove Default Encode URI ComponentCompare Source
No changes to path rules since 3.x, except support for nested RegEx parts in 4.x.
Changed
RegexpOptions
interface toTokensToRegexpOptions
normalizePathname
from library, document solution in READMEencodeURIComponent
v4.0.5
: Decode URICompare Source
Removed
whitelist
in favor ofdecodeURI
(advanced behavior can happen outsidepath-to-regexp
)v4.0.4
: RemoveString#normalize
Compare Source
Fixed
String.prototype.normalize
to continue supporting IEv4.0.3
: Normalize Path WhitelistCompare Source
Added
/%.-
)v4.0.2
: AllowRegexpOptions
inmatch
Compare Source
Fixed
RegexpOptions
inmatch(...)
functionv4.0.1
: Fix Spelling of RegexpCompare Source
Fixed
regexp
spelling across 4.xv4.0.0
: ES2015 Package for BundlersCompare Source
All path rules are backward compatible with 3.x, except for nested
()
and other RegEx special characters that were previously ignored.Changed
match
does not default todecodeURIComponent
Added
normalizePathname
utility for supporting unicode paths in librariesConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.