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

fillwatcher

v0.0.6

Published

FillWatcher ==

Downloads

9

Readme

FillWatcher

A stream for use with files that pre-allocate a bunch of disk space, then fill it up.

Why?

Node has pipes, and pipes are great. However, in the instance of a program (in my case, Windows Media Center) pre-allocating a file, streams don't work correctly. It pipes beyond the actual end of a recording, and doesn't double-back when the content changes.

How?

It's gross! We maintain a buffer (size of your choosing) and cut it up into chunks (number of your choosing). Then we compare those chunks with our cached copy, and pipe through chunks that have changed.

How can it go wrong?

So many ways!

  • I've barely tested this.
  • If you don't set your buffer size high enough or your check interval small enough, the file will be written to faster than our checker can verify what has changed. So you might need to tweak these values for your personal setup.

How do I use it?

Example:

import FillWatcher from 'fillwatcher'
import filesizeParser from 'filesize-parser'
import fs from 'fs'

let file = process.argv[2]

let watcher = new FillWatcher({
    path: file,
    chunkSize: filesizeParser('1MB'),
    numberOfChunks: 10,
    readInterval: 10 // in ms
})

let out = fs.createWriteStream(__dirname + '/tvout')
watcher.pipe(out)