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

pagingfile

v0.1.0

Published

Readable stream from a random pagingfile with "tail -f"

Downloads

3

Readme

node-pagingfile

Recycle a temporary file into a stream in node

How to install

Install with npm

npm install --save pagingfile

How to use

The main idea behind this module is to serve a simple way to recycle data of processes with an output file back into the stream flow.

With .getPath(function(err, path){ ... }) you are able to get the path of the origin file for this stream. Now you are able to use your output data directly as readable stream.

var Pageingfile = require('pagingfile');

var paging

You are also able to "recycle" this data in stream, because this module misses every stream input from writable stream excerpts the end event. This is why you are able to make constructions like this

var functionThatOutputsToAFile;
var pagingfile = new Pagingfile();

pagingfile.on('data', function (chunk) {
    // Do something with this chunk...
});

pagingfile.getPath(function (err, path) {
    var 
    if (err) {
        return console.error('Not able to get a path...');
    }
    functionThatOutputsToAFile(path, function callback(err){
        if (err) {
            console.error('There was an error', err);
        }
        setTimeout(function () { // We must call this with a timeout because tail is
            pagingfile.end();    // slower then writing to file!
        }, 100);
    });
});

This module is written with jsdoc. You can compile the docs with The compiled jsdoc is also included in the module package on npm...