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

fs-readstream-progress

v0.0.5

Published

fs-readstream-progress

Downloads

6

Readme



What problem does this solve?

Track the progress of readStreams for Node fs or hyperdrive archives.

Install

npm install fs-readstream-progress

Usage

Use it like fs.createReadStream, except that:

  • it also emits progress events
  • you can pass an alternative fs
  • it has a convenient .drain() method

API:

var getwithprogress = require('fs-readstream-progress')

var stream = getwithprogress(filename, opts)

Progress events

Example:

var progress = require('fs-readstream-progress')

progress('somefile')
  .on('progress', function (data) { console.log('progress:', data) })
  .on('data', function(data) {})
  .on('end', function() { console.log('done') })

Each progress event looks like:

{
  done: 16, // integer, number of bytes streamed so far
  total: 256, // integer, total number of bytes
  progress: 0.0625 // float, proportion of the data streamed
}

When all the data have been streamed, the stream will emit end, just like fs.createReadStream.

Different fs

To use a different fs implementation (e.g. a hyperdrive archive), just pass

var hyperdrive = require('hyperdrive')
var getwithprogress = require('fs-readstream-progress')

var archive = hyperdrive('.')
var stream = getwithprogress('somefile', { fs: archive })

.drain()

Drains the stream, pulling all data through without keeping it in memory.

This is useful if you just want to track a download from a hyperdrive archive.

License

To the extent possible by law, we transfer any rights we have in this code to the public domain. Specifically, we do so using the CC0 1.0 Universal Public Domain Dedication.

You can do whatever you want with this code. No need to credit us, link to us, include any license, or anything else. But if you want to do those things, you're free to do that too.