Turn a path string such as
/user/:nameinto a regular expression.
npm install path-to-regexp --save
const pathToRegexp = require('path-to-regexp')
// pathToRegexp(path, keys?, options?)
// pathToRegexp.parse(path)
// pathToRegexp.compile(path)
true the regexp will be case sensitive. (default: false)true the regexp allows an optional trailing delimiter to match. (default: false)true the regexp will match to the end of the string. (default: true)true the regexp will match from the beginning of the string. (default: true)'/')undefined, any character)const keys = []
const regexp = pathToRegexp('/foo/:bar', keys)
// regexp = /^\/foo\/([^\/]+?)\/?$/i
// keys = [{ name: 'bar', prefix: '/', delimiter: '/', optional: false, repeat: false, pattern: '[^\\/]+?' }]
undefinedPlease note: The RegExp returned by path-to-regexp is intended for ordered data (e.g. pathnames, hostnames). It can not handle arbitrarily ordered data (e.g. query strings, URL fragments, JSON, etc).
The path argument is used to define parameters and populate the list of keys.
Named parameters are defined by prefixing a colon to the parameter name (:foo). By default, the parameter will match until the next prefix (e.g. [^/]+).
const regexp = pathToRegexp('/:foo/:bar')
// keys = [{ name: 'foo', prefix: '/', ... }, { name: 'bar', prefix: '/', ... }]
regexp.exec('/test/route')
//=> [ '/test/route', 'test', 'route', index: 0, input: '/test/route', groups: undefined ]
undefinedPlease note: Parameter names must use “word characters” ([A-Za-z0-9_]).
Parameters can be suffixed with a question mark (?) to make the parameter optional.
const regexp = pathToRegexp('/:foo/:bar?')
// keys = [{ name: 'foo', ... }, { name: 'bar', delimiter: '/', optional: true, repeat: false }]
regexp.exec('/test')
//=> [ '/test', 'test', undefined, index: 0, input: '/test', groups: undefined ]
regexp.exec('/test/route')
//=> [ '/test/route', 'test', 'route', index: 0, input: '/test/route', groups: undefined ]
undefinedTip: The prefix is also optional, escape the prefix \/ to make it required.
Parameters can be suffixed with an asterisk (*) to denote a zero or more parameter matches. The prefix is used for each match.
const regexp = pathToRegexp('/:foo*')
// keys = [{ name: 'foo', delimiter: '/', optional: true, repeat: true }]
regexp.exec('/')
//=> [ '/', undefined, index: 0, input: '/', groups: undefined ]
regexp.exec('/bar/baz')
//=> [ '/bar/baz', 'bar/baz', index: 0, input: '/bar/baz', groups: undefined ]
Parameters can be suffixed with a plus sign (+) to denote a one or more parameter matches. The prefix is used for each match.
const regexp = pathToRegexp('/:foo+')
// keys = [{ name: 'foo', delimiter: '/', optional: false, repeat: true }]
regexp.exec('/')
//=> null
regexp.exec('/bar/baz')
//=> [ '/bar/baz','bar/baz', index: 0, input: '/bar/baz', groups: undefined ]
It is possible to write an unnamed parameter that only consists of a matching group. It works the same as a named parameter, except it will be numerically indexed.
const regexp = pathToRegexp('/:foo/(.*)')
// keys = [{ name: 'foo', ... }, { name: 0, ... }]
regexp.exec('/test/route')
//=> [ '/test/route', 'test', 'route', index: 0, input: '/test/route', groups: undefined ]
All parameters can have a custom regexp, which overrides the default match ([^/]+). For example, you can match digits or names in a path:
const regexpNumbers = pathToRegexp('/icon-:foo(\\d+).png')
// keys = [{ name: 'foo', ... }]
regexpNumbers.exec('/icon-123.png')
//=> ['/icon-123.png', '123']
regexpNumbers.exec('/icon-abc.png')
//=> null
const regexpWord = pathToRegexp('/(user|u)')
// keys = [{ name: 0, ... }]
regexpWord.exec('/u')
//=> ['/u', 'u']
regexpWord.exec('/users')
//=> null
undefinedTip: Backslashes need to be escaped with another backslash in JavaScript strings.
The parse function is exposed via pathToRegexp.parse. This will return an array of strings and keys.
const tokens = pathToRegexp.parse('/route/:foo/(.*)')
console.log(tokens[0])
//=> "/route"
console.log(tokens[1])
//=> { name: 'foo', prefix: '/', delimiter: '/', optional: false, repeat: false, pattern: '[^\\/]+?' }
console.log(tokens[2])
//=> { name: 0, prefix: '/', delimiter: '/', optional: false, repeat: false, pattern: '.*' }
undefinedNote: This method only works with strings.
Path-To-RegExp exposes a compile function for transforming a string into a valid path.
const toPath = pathToRegexp.compile('/user/:id')
toPath({ id: 123 }) //=> "/user/123"
toPath({ id: 'café' }) //=> "/user/caf%C3%A9"
toPath({ id: '/' }) //=> "/user/%2F"
toPath({ id: ':/' }) //=> "/user/%3A%2F"
toPath({ id: ':/' }, { encode: (value, token) => value }) //=> "/user/:/"
const toPathRepeated = pathToRegexp.compile('/:segment+')
toPathRepeated({ segment: 'foo' }) //=> "/foo"
toPathRepeated({ segment: ['a', 'b', 'c'] }) //=> "/a/b/c"
const toPathRegexp = pathToRegexp.compile('/user/:id(\\d+)')
toPathRegexp({ id: 123 }) //=> "/user/123"
toPathRegexp({ id: '123' }) //=> "/user/123"
toPathRegexp({ id: 'abc' }) //=> Throws `TypeError`.
toPathRegexp({ id: 'abc' }, { validate: true }) //=> "/user/abc"
undefinedNote: The generated function will throw on invalid input. It will do all necessary checks to ensure the generated path is valid. This method only works with strings.
Path-To-RegExp exposes the two functions used internally that accept an array of tokens.
pathToRegexp.tokensToRegExp(tokens, keys?, options?) Transform an array of tokens into a matching regular expression.pathToRegexp.tokensToFunction(tokens) Transform an array of tokens into a path generator function.name The name of the token (string for named or number for index)prefix The prefix character for the segment (e.g. /)delimiter The delimiter for the segment (same as prefix or default delimiter)optional Indicates the token is optional (boolean)repeat Indicates the token is repeated (boolean)pattern The RegExp used to match this token (string)Path-To-RegExp breaks compatibility with Express <= 4.x:
RegExp special characters regardless of position - this considered a bug*, + and ?. E.g. /:user**) - use parameters instead ((.*))Includes a .d.ts file for TypeScript users.
You can see a live demo of this library in use at express-route-tester.
MIT
We use cookies
We use cookies to analyze traffic and improve your experience. You can accept or reject analytics cookies.