</>PackageGraphPackageGraph

range-parser

npmv1.3.0

Range header field string parser

Safe to adopt

Yes — range-parser scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 76 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • AMaintenance: grade A, Excellent.

    Last published 76 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 8.8 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 range-parser to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

8.8 KB
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
node >= 0.6
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the range-parser README.

jsFull README ↗
var parseRange = require('range-parser')

range-parser vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
range-parserthis page02MIT2 months ago
commander451.1M11MIT1 day ago
postcss249.3M7MIT1 day ago
content-type191.4M6MIT1 day ago
negotiator183.3M2MIT1 day ago
yargs-parser178.8M2ISC1 day ago

Dependencies

Declared by range-parser v1.3.0. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (10)

deep-equal 1.0.1eslint 6.0.1eslint-config-standard 13.0.1eslint-plugin-import 2.18.0eslint-plugin-markdown 1.0.0eslint-plugin-node 9.1.0eslint-plugin-promise 4.2.1eslint-plugin-standard 4.0.0mocha 6.1.4nyc 14.1.1

Used by

Popular packages that depend on range-parser.

sendnpm

Better streaming static file server with Range and conditional-GET support

↓ 127.6M/wk◈ 3 dependents⚖ MIT
expressnpm

Fast, unopinionated, minimalist web framework

↓ 92.8M/wk◈ 17 dependents⚖ MIT

Relationship graph

Dependencies (left) and dependents (right) of range-parser.

sendexpressrange-parser
range-parser dependencies dependents

Frequently installed together

mime-typesnpm

The ultimate javascript content-type utility.

↓ 185.3M/wk◈ 9 dependents⚖ MIT
http-errorsnpm

Create HTTP error objects

↓ 149.4M/wk◈ 7 dependents⚖ MIT
eslintnpm

An AST-based pattern checker for JavaScript.

↓ 138.4M/wk◈ 279 dependents⚖ MITTS
encodeurlnpm

Encode a URL to a percent-encoded form, excluding already-encoded sequences

↓ 133.6M/wk◈ 5 dependents⚖ MIT
etagnpm

Create simple HTTP ETags

↓ 100M/wk◈ 4 dependents⚖ MIT
on-finishednpm

Execute a callback when a request closes, finishes, or errors

↓ 96.7M/wk◈ 5 dependents⚖ MIT
debugnpm

Lightweight debugging utility for Node.js and the browser

↓ 0/wk◈ 46 dependents⚖ MIT
statusesnpm

HTTP status utility

↓ 0/wk◈ 6 dependents⚖ MIT
escape-htmlnpm

Escape string for use in HTML

↓ 0/wk◈ 7 dependents⚖ MIT
freshnpm

HTTP response freshness testing

↓ 0/wk◈ 3 dependents⚖ MIT
content-typenpm

Create and parse HTTP Content-Type header

↓ 191.4M/wk◈ 6 dependents⚖ MITTS
finalhandlernpm

Node.js final http responder

↓ 132.1M/wk◈ 3 dependents⚖ MIT

Release history

1 release in the last two years, typically about 197 days apart.

Recent versions of range-parser
VersionPublishedSizeLicense
1.3.0latest2 months ago8.8 KBMIT
1.2.17 years ago8.3 KBMIT
1.2.010 years ago—MIT
1.1.010 years ago—MIT
1.0.311 years ago—MIT
1.0.212 years ago—MIT
1.0.112 years ago—MIT
1.0.012 years ago—MIT
0.0.414 years ago—MIT
0.0.314 years ago—MIT
0.0.214 years ago—MIT
0.0.114 years ago—MIT

Overview

range-parser is an npm package that range header field string parser. It has 2 known dependents in the graph. The latest version is 1.3.0, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need range header field string parser and value a focused solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Clear open-source license (MIT).

Cons

  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

blakeembreydougwilsonjonathanongjongleberrytjholowaychukulisesgascon

Keywords

httpparserrange

Funding

Frequently asked questions

Should I use range-parser?

Yes — range-parser scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 76 days ago.

How do I install range-parser?

Run `npm install range-parser` to add range-parser to your npm project.

What license is range-parser released under?

range-parser is distributed under the MIT license.

How popular is range-parser?

npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on range-parser.

Is range-parser still maintained?

The most recent release of range-parser (v1.3.0) was published 2 months ago.

Does range-parser run install scripts?

No. range-parser does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.