Back to Explore

jshttp/range-parser

GitHub
1 watchersOpen source

Last release: 5/11/2019

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

  • The repository appears to be maintained, with a recorded upstream push on 2026-02-02, though the most recent published update versions in the provided history are older (v1.2.1 in 2019).
  • Apparent update cadence is low, with published versions in 2016 (v1.1.0, v1.2.0) and 2019 (v1.2.1), suggesting infrequent, maintenance-style updates rather than regular feature releases.

AI summary generated Today

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • v1.2.1

    5/11/2019

    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

    6/1/2016

    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.

    Features
  • v1.1.0

    5/13/2016

    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

    10/29/2015

    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

    9/9/2014

    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.

    Features
  • v1.0.1

    9/8/2014

    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.

    Features
  • v1.0.0

    12/11/2013

    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

    6/18/2012

    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

    6/18/2012

    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.

    Breaking
  • v0.0.2

    6/14/2012

    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.