range-parser is a Node.js module for parsing the HTTP Range header field. It turns a range request into subranges for a given representation size, and returns negative values for malformed headers (-2) or unsatisfiable ranges (-1), with an option to combine overlapping or adjacent ranges.
Project status
- Actively maintained: Yes, upstream shows a recent push on 2026-06-25, and the latest published update v1.3.0 (2026-06-25) indicates ongoing maintenance rather than dormancy.
- Update cadence: After a long period without new published updates (next prior item shown is v1.2.1 from 2019-05-11), there are recent rapid updates in late June 2026, suggesting activity resumed, but the evidence does not confirm a steady ongoing cadence.
AI summary generated
Recent updates
v1.3.0
v1.3.0 focuses on hardening range parsing logic. It improves number parsing and adds handling for invalid start and end byte positions when parsing byte ranges, preventing incorrect parsing behavior on malformed inputs.
v1.2.1
v1.2.1 introduces stricter runtime validation for the range-parser input, adding an explicit type check for the `str` argument in `rangeParser`. The release notes section is empty, but the code diff also modernizes the repository toolchain (eslint, mocha, nyc) and CI configuration.
v1.2.0
No publisher release notes were provided for v1.2.0. The code changes add support for an optional `options` argument to `range-parser`, primarily introducing a `combine` option to merge overlapping and adjacent byte ranges.
Featuresv1.1.0
This release (v1.1.0) was published on 2016-05-13, but no release notes were provided by the publisher. Because the release notes are missing, there is not enough information to identify new features, breaking changes, bug fixes, security updates, or migration steps.
v1.0.3
Release v1.0.3 contains no publisher-provided release notes. The code changes are small and mainly consist of enabling strict mode in index.js, plus build/CI and documentation/test updates.
v1.0.2
No publisher release notes were provided for v1.0.2. The code diff shows this version primarily updates project metadata and CI to add Node.js 0.6 support, along with documentation/packaging housekeeping changes.
Featuresv1.0.1
v1.0.1 does not include any application code changes in the provided diff, and there are no release notes from the publisher. The update focuses on package metadata, test tooling, and CI/coverage configuration, along with some documentation cleanup and repository/license publishing adjustments.
Featuresv1.0.0
Release v1.0.0 updates package metadata and documentation, adding repository information and the MIT license text. No functional code changes are shown in the provided diff, only README and package.json metadata plus a changelog entry in History.md.
v0.0.4
Release v0.0.4 contains no publisher-provided release notes. The code change centers on changing the parser's return values for invalid input and unsatisfiable ranges.
v0.0.3
Version v0.0.3 makes a small but behavior-affecting change to the range parsing logic. It caps the computed end position to the available resource length minus one, and adds/adjusts tests to reflect the corrected behavior.
Breakingv0.0.2
Release v0.0.2 was published, but the publisher did not provide any release notes. No documented changes (features, fixes, breaking changes, security, performance, or migration guidance) are available to assess developer impact.