npmpackage.info

Gathering detailed insights and metrics for path-to-regexp

Other packages similar to path-to-regexp

@qixian.cs/path-to-regexp

6.1.0

Express style path to RegExp utility

path-match

1.2.4

wrapper around path-to-regexp for easy route parameters

micromatch

4.0.8

Glob matching for javascript/node.js. A replacement and faster alternative to minimatch and multimatch.

@stdlib/regexp-extended-length-path

0.2.2

Regular expression to detect an extended-length path.

Gathering detailed insights and metrics for path-to-regexp

path-to-regexp

Turn a path string such as `/user/:name` into a regular expression

8.2.0

8,268

MIT

TypeScript

2.09 kB

10,768,234,343 5.1

Installations

npm install path-to-regexp

Developer Guide

BETA

Typescript

No

Module System

CommonJS, ESM

Min. Node Version

>=16

Node Version

20.12.1

NPM Version

10.5.0 Score

99.8

Supply Chain

99.5

Quality

90.9

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

1

Total

111

Closed

34

Merged

76

Issues

Open

2

Total

214

Closed

212

Releases

Fix backtracking (again)

v0.1.12

Published on 05 Dec 2024

8.2.0

v8.2.0

Published on 26 Sept 2024

Error on bad input

v0.1.11

Published on 12 Sept 2024

Fix backtracking in 6.x

v6.3.0

Published on 12 Sept 2024

Add backtracking protection

v3.3.0

Published on 10 Sept 2024

Fix backtracking in 1.x

v1.9.0

Published on 10 Sept 2024

View all 29 releases

Contributors

View all 51 contributors

Languages

TypeScript

TypeScript (100%)

Developer

pillarjs

Download Statistics

Total Downloads

10,768,234,343

Last Day

11,449,076

Last Week

51,953,469

Last Month

228,966,815

Last Year

2,706,882,253

GitHub Statistics

8,268 Stars

343 Commits

389 Forks

64 Watching

6 Branches

51 Contributors

Bundle Size

5.00 kB

Minified

2.09 kB

Minified + Gzipped

Bundlephobia

Maintainers

Package Meta Information

Latest Version

8.2.0

Package Id

path-to-regexp@8.2.0

Unpacked Size

53.95 kB

Size

13.17 kB

File Count

NPM Version

10.5.0

Node Version

20.12.1

Publised On

26 Sept 2024

Total Downloads

Cumulative downloads

Total Downloads

10,768,234,343

Last day

-1.3%

11,449,076

Compared to previous day

Last week

-13.5%

51,953,469

Compared to previous week

Last month

4.7%

228,966,815

Compared to previous month

Last year

13.7%

2,706,882,253

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

@borderless/ts-scripts @size-limit/preset-small-lib @types/node @types/semver @vitest/coverage-v8 recheck size-limit typescript

Versions

Path-to-RegExp

Turn a path string such as /user/:name into a regular expression.

Installation

npm install path-to-regexp --save

Usage

1const {
2  match,
3  pathToRegexp,
4  compile,
5  parse,
6  stringify,
7} = require("path-to-regexp");

Parameters

Parameters match arbitrary strings in a path by matching up to the end of the segment, or up to any proceeding tokens. They are defined by prefixing a colon to the parameter name (:foo). Parameter names can use any valid JavaScript identifier, or be double quoted to use other characters (:"param-name").

1const fn = match("/:foo/:bar");
2
3fn("/test/route");
4//=> { path: '/test/route', params: { foo: 'test', bar: 'route' } }

Wildcard

Wildcard parameters match one or more characters across multiple segments. They are defined the same way as regular parameters, but are prefixed with an asterisk (*foo).

1const fn = match("/*splat");
2
3fn("/bar/baz");
4//=> { path: '/bar/baz', params: { splat: [ 'bar', 'baz' ] } }

Optional

Braces can be used to define parts of the path that are optional.

1const fn = match("/users{/:id}/delete");
2
3fn("/users/delete");
4//=> { path: '/users/delete', params: {} }
5
6fn("/users/123/delete");
7//=> { path: '/users/123/delete', params: { id: '123' } }

Match

The match function returns a function for matching strings against a path:

path String or array of strings.
options (optional) (Extends pathToRegexp options)
- decode Function for decoding strings to params, or false to disable all processing. (default: decodeURIComponent)

1const fn = match("/foo/:bar");

Please note: path-to-regexp is intended for ordered data (e.g. paths, hosts). It can not handle arbitrarily ordered data (e.g. query strings, URL fragments, JSON, etc).

PathToRegexp

The pathToRegexp function returns a regular expression for matching strings against paths. It

path String or array of strings.
options (optional) (See parse for more options)
- sensitive Regexp will be case sensitive. (default: false)
- end Validate the match reaches the end of the string. (default: true)
- delimiter The default delimiter for segments, e.g. [^/] for :named parameters. (default: '/')
- trailing Allows optional trailing delimiter to match. (default: true)

1const { regexp, keys } = pathToRegexp("/foo/:bar");

Compile ("Reverse" Path-To-RegExp)

The compile function will return a function for transforming parameters into a valid path:

path A string.
options (See parse for more options)
- delimiter The default delimiter for segments, e.g. [^/] for :named parameters. (default: '/')
- encode Function for encoding input strings for output into the path, or false to disable entirely. (default: encodeURIComponent)

1const toPath = compile("/user/:id");
2
3toPath({ id: "name" }); //=> "/user/name"
4toPath({ id: "café" }); //=> "/user/caf%C3%A9"
5
6const toPathRepeated = compile("/*segment");
7
8toPathRepeated({ segment: ["foo"] }); //=> "/foo"
9toPathRepeated({ segment: ["a", "b", "c"] }); //=> "/a/b/c"
10
11// When disabling `encode`, you need to make sure inputs are encoded correctly. No arrays are accepted.
12const toPathRaw = compile("/user/:id", { encode: false });
13
14toPathRaw({ id: "%3A%2F" }); //=> "/user/%3A%2F"

Stringify

Transform TokenData (a sequence of tokens) back into a Path-to-RegExp string.

data A TokenData instance

1const data = new TokenData([
2  { type: "text", value: "/" },
3  { type: "param", name: "foo" },
4]);
5
6const path = stringify(data); //=> "/:foo"

Developers

If you are rewriting paths with match and compile, consider using encode: false and decode: false to keep raw paths passed around.
To ensure matches work on paths containing characters usually encoded, such as emoji, consider using encodeurl for encodePath.

Parse

The parse function accepts a string and returns TokenData, the set of tokens and other metadata parsed from the input string. TokenData is can used with match and compile.

path A string.
options (optional)
- encodePath A function for encoding input strings. (default: x => x, recommended: encodeurl)

Tokens

TokenData is a sequence of tokens, currently of types text, parameter, wildcard, or group.

Custom path

In some applications, you may not be able to use the path-to-regexp syntax, but still want to use this library for match and compile. For example:

1import { TokenData, match } from "path-to-regexp";
2
3const tokens = [
4  { type: "text", value: "/" },
5  { type: "parameter", name: "foo" },
6];
7const path = new TokenData(tokens);
8const fn = match(path);
9
10fn("/test"); //=> { path: '/test', index: 0, params: { foo: 'test' } }

Errors

An effort has been made to ensure ambiguous paths from previous releases throw an error. This means you might be seeing an error when things worked before.

Unexpected `?` or `+`

In past releases, ?, *, and + were used to denote optional or repeating parameters. As an alternative, try these:

For optional (?), use an empty segment in a group such as /:file{.:ext}.
For repeating (+), only wildcard matching is supported, such as /*path.
For optional repeating (*), use a group and a wildcard parameter such as /files{/*path}.

Unexpected `(`, `)`, `[`, `]`, etc.

Previous versions of Path-to-RegExp used these for RegExp features. This version no longer supports them so they've been reserved to avoid ambiguity. To use these characters literally, escape them with a backslash, e.g. "\\(".

Missing parameter name

Parameter names must be provided after : or *, and they must be a valid JavaScript identifier. If you want an parameter name that isn't a JavaScript identifier, such as starting with a number, you can wrap the name in quotes like :"my-name".

Unterminated quote

Parameter names can be wrapped in double quote characters, and this error means you forgot to close the quote character.

Express <= 4.x

Path-To-RegExp breaks compatibility with Express <= 4.x in the following ways:

The wildcard * must have a name, matching the behavior of parameters :.
The optional character ? is no longer supported, use braces instead: /:file{.:ext}.
Regexp characters are not supported.
Some characters have been reserved to avoid confusion during upgrade (()[]?+!).
Parameter names now support valid JavaScript identifiers, or quoted like :"this".

License

MIT

Stable Version

8.2.0

HIGH

0/10

Summary

Unpatched `path-to-regexp` ReDoS in 0.1.x

Affected Versions

< 0.1.12

Patched Versions

0.1.12

HIGH

7.5/10

Summary

path-to-regexp outputs backtracking regular expressions

Affected Versions

>= 4.0.0, < 6.3.0

Patched Versions

6.3.0

HIGH

7.5/10

Summary

path-to-regexp outputs backtracking regular expressions

Affected Versions

>= 7.0.0, < 8.0.0

Patched Versions

8.0.0

HIGH

7.5/10

Summary

path-to-regexp outputs backtracking regular expressions

Affected Versions

>= 2.0.0, < 3.3.0

Patched Versions

3.3.0

HIGH

7.5/10

Summary

path-to-regexp outputs backtracking regular expressions

Affected Versions

>= 0.2.0, < 1.9.0

Patched Versions

1.9.0

HIGH

7.5/10

Summary

Dependency-Update-Tool

Determines if the project uses a dependency update tool.

0

Fuzzing

Determines if the project uses fuzzing.

Reason

project is not fuzzed

Details

Warn: no OSSFuzz integration found: Follow the steps in https://github.com/google/oss-fuzz to integrate fuzzing for your project. Over time, try to add fuzzing for more functionalities of your project. (High effort)
Warn: no OneFuzz integration found: Follow the steps in https://github.com/microsoft/onefuzz to start fuzzing for your project. Over time, try to add fuzzing for more functionalities of your project. (High effort)
Warn: no GoBuiltInFuzzer integration found: Follow the steps in https://go.dev/doc/fuzz/ to enable fuzzing on your project. Over time, try to add fuzzing for more functionalities of your project. (Medium effort)
Warn: no PythonAtherisFuzzer integration found: Follow the steps in https://github.com/google/atheris to enable fuzzing on your project. Over time, try to add fuzzing for more functionalities of your project. (Medium effort)
Warn: no CLibFuzzer integration found: Follow the steps in https://llvm.org/docs/LibFuzzer.html to enable fuzzing on your project. Over time, try to add fuzzing for more functionalities of your project. (Medium effort)
Warn: no CppLibFuzzer integration found: Follow the steps in https://llvm.org/docs/LibFuzzer.html to enable fuzzing on your project. Over time, try to add fuzzing for more functionalities of your project. (Medium effort)
Warn: no SwiftLibFuzzer integration found: Follow the steps in https://google.github.io/oss-fuzz/getting-started/new-project-guide/swift-lang/ to enable fuzzing on your project. Over time, try to add fuzzing for more functionalities of your project. (Medium effort)
Warn: no RustCargoFuzzer integration found: Follow the steps in https://rust-fuzz.github.io/book/cargo-fuzz.html to enable fuzzing on your project. Over time, try to add fuzzing for more functionalities of your project. (Medium effort)
Warn: no JavaJazzerFuzzer integration found: Follow the steps in https://github.com/CodeIntelligenceTesting/jazzer to enable fuzzing on your project. Over time, try to add fuzzing for more functionalities of your project. (Medium effort)
Warn: no ClusterFuzzLite integration found: Follow the steps in https://github.com/google/clusterfuzzlite to integrate fuzzing as part of CI. Over time, try to add fuzzing for more functionalities of your project. (High effort)
Warn: no HaskellPropertyBasedTesting integration found: Use one of the following frameworks to fuzz your project: QuickCheck: https://hackage.haskell.org/package/QuickCheck hedgehog: https://hedgehog.qa/ validity: https://github.com/NorfairKing/validity smallcheck: https://hackage.haskell.org/package/smallcheck hspec: https://hspec.github.io/ tasty: https://hackage.haskell.org/package/tasty (High effort)
Warn: no TypeScriptPropertyBasedTesting integration found: Use fast-check: https://github.com/dubzzz/fast-check (High effort)
Warn: no JavaScriptPropertyBasedTesting integration found: Use fast-check: https://github.com/dubzzz/fast-check (High effort)

0

SAST

Determines if the project uses static code analysis.

Score

5.1

/10

Last Scanned on 2025-01-27T21:24:10Z

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More

Other packages similar to path-to-regexp

Other packages similar to path-to-regexp

path-to-regexp

Installations

Developer Guide

No

CommonJS, ESM

>=16

20.12.1

10.5.0

Score

Pull Requests

1

111

34

76

Issues

2

214

212

Releases

Contributors

Languages

Developer

pillarjs

Download Statistics

GitHub Statistics

Bundle Size

5.00 kB

2.09 kB

Maintainers

Package Meta Information

Total Downloads

10,768,234,343

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

Path-to-RegExp

Installation

Usage

Parameters

Wildcard

Optional

Match

PathToRegexp

Compile ("Reverse" Path-To-RegExp)

Stringify

Developers

Parse

Tokens

Custom path

Errors

Unexpected ? or +

Unexpected (, ), [, ], etc.

Missing parameter name

Unterminated quote

Express <= 4.x

License

Stable Version

8.2.0

HIGH

10

10

10

10

10

10

10

7

6

2

0

0

0

0

0

0

5.1

Unexpected `?` or `+`

Unexpected `(`, `)`, `[`, `]`, etc.