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

@cool-blue/brout

v1.1.3

Published

stdout and stderr for browsers

Downloads

3

Readme

stdout and stderr for browsers

Installs process.stdout and process.stderr and redirects console like node.

Repository: https://github.com/mantoni/brout.js


Install with npm

npm install brout

Usage

Assume my-script.js contains this:

process.stdout.write('Hello stdout!\n');
console.log('Hello %s!', 'console');

Use with browserify and phantomic:

$ browserify -t brout my-script.js | phantomic
Hello stdout!
Hello console!

API

var brout = require('brout');

brout.on('out', function (str)) {
  // ...
});

brout.on('err', function (str)) {
  // ...
});

brout.on('exit', function (code)) {
  // ...
});

Event listeners are tiggered by these calls:

  • process.stdout.write(string)
  • process.stderr.write(string)
  • process.exit(code)

The console functions log, info, warn and error get replaced and the original implementation is exposed:

  • console.log.original
  • console.info.original
  • console.warn.original
  • console.error.original

The console override behaves like node's implementation and writes to process.stdout and process.sterr.

If an out or err listener is installed, then the corresponding console message is no longer forwarded to the original console implementation.

License

MIT