path-to-regexp

9.0.0 · 22 Oct 2026MIT310.6M / weekRepository Homepage npm Atom feed

Upgrading path-to-regexp From 6.2.0 to 6.2.1

Same major only

1 release in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 6.2.0Newest 6.x, Clears its advisory6.3.0 Latest9.0.0

6.2.0yours
6.2.1target

0
changes to make: 0
advisories fixed: 1
new: 1
fix

Security

1 advisory still affects 6.2.1

path-to-regexp outputs backtracking regular expressionshigh · GHSA-9wv6-86v2-598j

Upgrading to 6.3.0 clears it.

Release by release

6.2.1
6 May 20221 new · 1 fix
- new
  New example in documentation (#256) ae9e576
- fixed
  Fix invalid matching of :name* parameter (#261) 762bc6b

3 other lines we could not sort, mostly version bumps

Compare delimiter string over regexp 86baef8
6.2.1
Update demo link (#250) 77df638
6.2.1
Update README encode example b39edd4
6.2.1

Upgrade to 6.2.1

npm install path-to-regexp@6.2.1

What 6.2.1 needs

Reading 6.2.1's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 6.2.1. Read once, not stored.

After upgrading

Run the type checker, the linter and the tests.
Build, and look for new deprecation warnings.
Update peer dependencies the new version asks for.
1 advisory still affects 6.2.1.