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

stdout-monkey

v1.1.0

Published

who said bananas? was it you?

Downloads

2

Readme

stdout-monkey

Monkeypatch for stdout with knobs. For testing purposes, or other things.

install

npm install stdout-monkey

example

var stdout = require('stdout-monkey');

var monkey = stdout(function(str, enc, cb){
  this.log('I want more bananas!');
})

console.log('Hey, stop it!');
// -> I want more bananas!

why

You don't want to spam stdout for testing. You want to batch data or you want to transform data before it reaches stdout.

api

Below when I write stdout I really want to write process.stdout.write.

var monkey = require('stdout-monkey')([callback])

Calling the module with a function returns a monkeypatched stdout disabled by default. Instead the arguments are passed to the given callback.

Note: that is not really accurate since the object is not a writable stream.

monkey.patch([callback])

Default method returned from the module. Patch stdout and disable it. Use the given callback instead. Returns the monkey instance.

monkey.restore([data], [enc], [cb])

Restore stdout. Optionaly write something.

monkey.listen([callback])

Patch stdout but only to include the callback. stdout will work as normal, you can spy but not modify what is written.

monkey.write(data, [enc], [cb])

Use the original process.stdout.write even if it was patched.

monkey.log([arguments])

Use console.log even if stdout was patched.

All above methods are chainable.

properties

The monkey has a state property indicating if process.stdout.write was patched or if he used the restore or listen methods.

NOTE: the state is not changed when calling the log or write methods.

test

npm test

inspirated and based on

todo

  • [ ] make the monkey a through stream.

license