to-regex-range 2.1.1

Pass two numbers, get a regex-compatible source string for matching ranges. Validated against more than 2.78 million test assertions.

to-regex-range@2.1.1 was published on 2017-04-27. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.10.0.

All to-regex-range versions · Permanent reference to 2.1.1 · Latest release

Package specifications

Version2.1.1
License declarationMIT
Published2017-04-27T13:34:30.544Z
Node.js requirement>=0.10.0
Type declarationsNot declared
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies4
Repository starsUnknown
Repository forksUnknown

Install to-regex-range 2.1.1

npm install to-regex-range@2.1.1
pnpm add to-regex-range@2.1.1
yarn add to-regex-range@2.1.1

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

Evidence and freshness