path-to-regexp
npmv8.4.2TypeScriptExpress style path to RegExp utility
Safe to adopt
Yes — path-to-regexp scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 161 days ago. 13 releases in the last 2 years.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- BMaintenance: grade B, Good.
Last published 161 days ago. 13 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 58 KB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 6 maintainers, and a contained dependency surface.
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding path-to-regexp to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- No constraint declared
- Module format
- CommonJS only
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the path-to-regexp README.
const {
match,
pathToRegexp,
compile,
parse,
stringify,
} = require("path-to-regexp");path-to-regexp vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| path-to-regexpthis page | 0 | 2 | MIT | 5 months ago |
| escape-string-regexp | 361M | 8 | MIT | 6 days ago |
| express | 132.9M | 17 | MIT | 6 days ago |
| is-regex | 104.2M | 1 | MIT | 6 days ago |
| cors | 76.8M | 6 | MIT | 6 days ago |
| balanced-match | 0 | 1 | MIT | 6 days ago |
Dependencies
Declared by path-to-regexp v8.4.2. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (9)
Used by
Popular packages that depend on path-to-regexp.
Relationship graph
Dependencies (left) and dependents (right) of path-to-regexp.
Frequently installed together
A collection of essential TypeScript types
An extremely fast JavaScript and CSS bundler and minifier.
An HTTP/1.1 client, written from scratch for Node.js
Deprecate all the things
Node.js final http responder
Fast, unopinionated, minimalist web framework
Prettier is an opinionated code formatter
Promise based HTTP client for the browser and node.js
Next generation testing framework powered by Vite
A JavaScript implementation of many web standards
Packs ECMAScript/CommonJs/AMD modules for the browser. Allows you to split your codebase into multiple bundles, which can be loaded on demand. Supports loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
A Query Language and Runtime which can target any service.
Release history
6 releases in the last two years, typically about 4 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 8.4.2latest | 5 months ago | 58 KB | MIT |
| 8.4.1 | 5 months ago | 59 KB | MIT |
| 8.4.0 | 5 months ago | 62 KB | MIT |
| 0.1.13 | 5 months ago | 6.5 KB | MIT |
| 8.3.0 | 1 year ago | 55 KB | MIT |
| 0.1.12 | 1 year ago | 6.4 KB | MIT |
| 8.2.0 | 1 year ago | 54 KB | MIT |
| 0.1.11 | 2 years ago | 6.4 KB | MIT |
| 6.3.0 | 2 years ago | 109 KB | MIT |
| 3.3.0 | 2 years ago | 25 KB | MIT |
| 1.9.0 | 2 years ago | 24 KB | MIT |
| 7.2.0 | 2 years ago | 64 KB | MIT |
| 8.1.0 | 2 years ago | 55 KB | MIT |
| 8.0.0 | 2 years ago | 50 KB | MIT |
| 0.1.10 | 2 years ago | 6.2 KB | MIT |
Overview
path-to-regexp is an npm package that express style path to RegExp utility. It has 2 known dependents in the graph. The latest version is 8.4.2, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need express style path to RegExp utility and value a focused solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.
Pros
- Ships TypeScript type definitions.
- Clear open-source license (MIT).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Funding
Frequently asked questions
Should I use path-to-regexp?
Yes — path-to-regexp scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 161 days ago. 13 releases in the last 2 years.
How do I install path-to-regexp?
Run `npm install path-to-regexp` to add path-to-regexp to your npm project.
What license is path-to-regexp released under?
path-to-regexp is distributed under the MIT license.
How popular is path-to-regexp?
npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on path-to-regexp.
Is path-to-regexp still maintained?
The most recent release of path-to-regexp (v8.4.2) was published 5 months ago.
Does path-to-regexp run install scripts?
No. path-to-regexp does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.