path-to-regexp
9.0.0 · 22 Oct 2026MIT310.6M / weekRepositoryHomepagenpmAtom feed
Upgrading path-to-regexp From 4.0.3 to 6.3.0
9 releases in betweennotes for 6
Reading releases, release notes and advisories…
- ?
- changes to make
- 1
- advisory fixed
- 6+
- new
- 1+
- fix
Counted from 6 of 9 release notes. Advisories are counted from the advisory database, in full.
Security
Fixes 1 advisory affecting 4.0.3
- path-to-regexp outputs backtracking regular expressionshigh · GHSA-9wv6-86v2-598j
Release by release
- new
Add backtrack protection to 6.x (#324) f1253b4
- new
6.2.2no release note
- new
New example in documentation (#256) ae9e576
- fixed
Fix invalid matching of
:name*parameter (#261) 762bc6b
- new
- new
Support named capturing groups for RegExps
- new
6.1.0nothing new or fixed in the note
- new
Support for nested non-capturing groups in regexp, e.g.
/(abc(?=d)) - new
Support for custom prefix and suffix groups using
/{abc(.*)def} - new
Add support for
{}to capture prefix/suffix explicitly, enables custom use-cases like/:attr1{-:attr2}?
- new
4.0.4 – 5.0.03 releases, nothing new or fixed; 2 without a note
11 other lines we could not sort, mostly version bumps
- 6.2.1
Compare delimiter string over regexp 86baef8
- 6.2.1
Update demo link (#250) 77df638
- 6.2.1
Update README encode example b39edd4
- 6.2.0
Update
strictflag documentation - 6.2.0
Ignore test files when bundling
- 6.1.0
Use
/#?as default delimiter to avoid matching on query or fragment parameters - 6.0.0
Tokens in an unexpected position will throw an error
- 6.0.0
Revert using any character as prefix, support
prefixesoption to configure this (starts as/.which acts like every version since 0.x again) - 5.0.0
Rename
RegexpOptionsinterface toTokensToRegexpOptions - 5.0.0
Remove
normalizePathnamefrom library, document solution in README