npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@indutny/range-finder

v1.3.4

Published

Reuse readable streams while serving range requests

Downloads

1,757

Readme

@indutny/range-finder

npm CI Status

API docs.

Reuse readable streams while serving range requests.

Typically range requests are made for a data directly available on the file system. However, for the cases where the data at rest is encrypted and not easily indexable, serving range request still requires decrypting file from the beginning. This can become a bottleneck for situations where a video has to be served to a browser, since for a 100MB video Chromium would typically make hundreds of requests, turning a 100MB video into tens of gigabytes of read and decrypted data.

range-finder is is an aid for these (perhaps niche) cases. Instead of creating a brand new stream for every request it stores and tracks previously created streams that were no fully read, and attempts to reuse them when requesting subsequent data. For the example of Chromium video loader above, using this module reduces the created streams from ~200 to ~3.

Installation

npm install @indutny/range-finder

Usage

import { RangeFinder, DefaultStorage } from '@indutny/range-finder';
import { createReadStream } from 'node:fs';

const storage = new DefaultStorage(() => createReadStream('/tmp/1.txt'), {
  maxSize: 100,
});

const finder = new RangeFinder(storage);

const startOffset = 123;
finder.get(startOffset).pipe(process.stdout);

Limitations

Because streams are reused between several requests, if one of the requests gets stalled it might stall all other requests that are based on the same input stream. Depending on the use case, either more granular contexts could be used or a timeout could be added to all derived streams.

LICENSE

This software is licensed under the MIT License.