Sourced from path-to-regexp's releases.
Fix backtracking in 1.x
Fixed
- Add backtrack protection to 1.x release (#320) 925ac8e
- Fix
re.exec(&[#39](https://github.com/pillarjs/path-to-regexp/issues/39);/test/route&[#39](https://github.com/pillarjs/path-to-regexp/issues/39);)
result (#267) 32a14b0https://github.com/pillarjs/path-to-regexp/compare/v1.8.0...v1.9.0
Backport token to function options
Added
- Backport
TokensToFunctionOptions
Fix backtracking (again)
Fixed
- Improved backtracking protection for 0.1.x, will break some previously valid paths (see previous advisory: https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j)
https://github.com/pillarjs/path-to-regexp/compare/v0.1.11...v0.1.12
Error on bad input
Changed
- Add error on bad input values 8f09549
https://github.com/pillarjs/path-to-regexp/compare/v0.1.10...v0.1.11
Sourced from path-to-regexp's changelog.
Moved to GitHub Releases
3.0.0 / 2019-01-13
- Always use prefix character as delimiter token, allowing any character to be a delimiter (e.g.
/:att1-:att2-:att3-:att4-:att5
)- Remove
partial
support, prefer escaping the prefix delimiter explicitly (e.g.\\/(apple-)?icon-:res(\\d+).png
)2.4.0 / 2018-08-26
- Support
start
option to disable anchoring from beginning of the string2.3.0 / 2018-08-20
- Use
delimiter
when processing repeated matching groups (e.g.foo/bar
has no prefix, but has a delimiter)2.2.1 / 2018-04-24
- Allow empty string with
end: false
to match both relative and absolute paths2.2.0 / 2018-03-06
- Pass
token
as second argument toencode
option (e.g.encode(value, token)
)2.1.0 / 2017-10-20
- Handle non-ending paths where the final character is a delimiter
- E.g.
/foo/
before required either/foo/
or/foo//
to match in non-ending mode2.0.0 / 2017-08-23
- New option! Ability to set
endsWith
to match paths like/test?query=string
up to the query string- New option! Set
delimiters
for specific characters to be treated as parameter prefixes (e.g./:test
)- Remove
isarray
dependency- Explicitly handle trailing delimiters instead of trimming them (e.g.
/test/
is now treated as/test/
instead of/test
when matching)- Remove overloaded
keys
argument that acceptedoptions
- Remove
keys
list attached to theRegExp
output- Remove asterisk functionality (it's a real pain to properly encode)
- Change
tokensToFunction
(e.g.compile
) to accept anencode
function for pretty encoding (e.g. pass your own implementation)1.7.0 / 2016-11-08
- Allow a
delimiter
option to be passed in withtokensToRegExp
which will be used for "non-ending" token match situations1.6.0 / 2016-10-03
- Populate
RegExp.keys
when using thetokensToRegExp
method (making it consistent with the main export)- Allow a
delimiter
option to be passed in withparse
- Updated TypeScript definition with
Keys
andOptions
updated1.5.3 / 2016-06-15
... (truncated)
c75eb10
1.9.0925ac8e
Add backtrack protection to 1.x release (#320)32a14b0
Fix re.exec('/test/route')
result (#267)79a5dcf
1.8.01a47442
feat: backport TokensToFunctionOptions to v1.x9c0550c
Update history for 1.7.0
a99ec3c
v1.7.069fb61b
Allow delimiter to be set for tokensToRegExp
1c2e8e4
Update history for 1.6.0
bdf17de
v1.6.0Sourced from express's releases.
4.21.2
What's Changed
- Add funding field (v4) by
@bjohansebas
in expressjs/express#6065- deps: path-to-regexp@0.1.11 by
@blakeembrey
in expressjs/express#5956- deps: bump path-to-regexp@0.1.12 by
@jonchurch
in expressjs/express#6209- Release: 4.21.2 by
@UlisesGascon
in expressjs/express#6094Full Changelog: https://github.com/expressjs/express/compare/4.21.1...4.21.2
Sourced from express's changelog.
4.21.2 / 2024-11-06
- deps: path-to-regexp@0.1.12
- Fix backtracking protection
- deps: path-to-regexp@0.1.11
- Throws an error on invalid path values
This version was pushed to npm by jonchurch, a new releaser for express since your current version.