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

crispy-stream

v0.1.2

Published

In-Memory Stream Implementation

Downloads

19

Readme

Crispy Stream

Build Status Code Climate Test Coverage

Lets imagine you want to test how a lib you created behaves when using its 'stream-mode' and, of course you don't want to read and write from file system. So what should you do? Well you should use this package which is an implementation of Stream.

Because this library implements Node's Stream abstract interface you can use it as you would any other Stream implementation.

Installation

 $ npm install crispy-stream

Require Crispy Stream

  var crispyStream = require('crispy-stream');

Read Stream.

Creating Read Stream Using a Factory.

If you prefer to have functions creating your streams rather than using the new operator yourself.

  // With buffer input.
  var buff = new Buffer('sample text');
  var readable = crispyStream.createReadStream(buff);

  // With simple string.
  var readable = crispyStream.createReadStream('sample text');

Creating New Read Stream Using The new Operator.

In case you fancy the Pseudo-classical way.

  var Readable = crispyStream.Readable;

  // With buffer input.
  var buff = new Buffer('sample text');
  var readable = new Readable(buff);

  // With simple string.
  var readable = new Readable('sample text');

Write Stream.

Creating Write Stream Using a Factory.

  var writable = crispyStream.createWriteStream();

Creating Write Stream Using The new Operator.

  var Writable = crispyStream.Writable;
  var writable = new Writable();

Piping.

Just as every stream library, you can pipe things from a read stream to a write stream.

Between Crispy Streams.

  var input = 'pipe this';
  var pipable = crispyStream.createReadStream(input);
  var writable = crispyStream.createWriteStream();

  pipable.pipe(writable);

Between Crispy Stream and Native Stream.

Native Readable to Crispy Writable

  var fs = require('fs');
  var input = '/path/to/input';
  var pipable = fs.createReadStream(input);
  var writable = crispyStream.createWriteStream();

  pipable.pipe(writable);

Crispy Readable to Native Writable

  var fs = require('fs');
  var input = 'pipe this';
  var filename = '/path/to/output';
  var pipable = crispyStream.createReadStream(input);
  var writable = fs.createWriteStream(filename);

  pipable.pipe(writable);