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

miniwrite

v0.1.4

Published

Minimal semantic output writer

Downloads

9,223

Readme

miniwrite

Build Status Dependency Status NPM version

Minimal output-stream writer API.

A pluggable output writer interface/adapter to embed/expose in tools and reporters, also a simplified stream.

This is not a logging framework or full console or stream replacement. Instead this is an abstraction to build on or expose in other tools. Intend as companion to ministyle (et al).

API

Main usage:

// simplified node.js.browser compatible console.log()
var mw = miniwrite.console();

// write plain text line
mw.writeln('hello world!');

Helpers

Buffer writes:

// buffer own lines
var mw = miniwrite.buffer();
// buffer other writes (handy for testing)
var mw = miniwrite.buffer(myMiniWrite);

// get buffer
var str = mw.concat();
var str = mw.concat('\n\n', '\t');
// iterate buffer if you must
mw.lines.forEach(function(line) {
	//..
})
// clear buffer
mw.clear();

Adapter to buffer character writes via mw.write(chars), auto-flushes on newlines:

var mw = miniwrite.chars(miniwrite.console());

// write plain text line
mw.write('hello');
mw.write(' ');
mw.writeln('world!'); // "hello world\n"

//or accumulate chars
mw.write('one');
mw.write('two');
mw.flush(true); // onetwo

// clear buffer
mw.write('one');
mw.clear();
mw.write('two');
mw.flush(true); // two

Spread of multiple writers

var mw = miniwrite.multi([myANSIConsole, myRemoteSocket, myDiskLogger]);
mw.enabled = true;
mw.targets.forEach(function(subw, num) {
	// .. 
});

Proxy to toggle stream or swap output target:

var mw = miniwrite.peek(myMiniWrite, callback);
mw.enabled = true;
mw.target = myOherWrite;
mw.callback = function(line) {
	// return string, or false to ignore
});

Proxy to toggle stream or swap output target:

var mw = miniwrite.proxy(myMiniWrite);
mw.enabled = true;
mw.target = myOherWrite;
mw.target = myOherWrite;

Convenience preset for grunt (same as in grunt ~0.4.1):

var mw = miniwrite.grunt(grunt);

Examples

Build your own:

var mw = {};
mw.writeln = function(line) {
	myWebSocketHyperStream.send({line: line})
};
// pass to supporting tools
awesomeModule.useMiniWritePlz(mw);

Tap into output

awesomeModule.writer = miniwrite.splitter([awesomeModule.writer, myMiniWrite]);

Installation

$ npm install miniwrite --save

History

  • 0.1.2 - Enabled strict mode, split in internal modules
  • 0.1.0 - Extracted styling to ministyle.
  • 0.0.1 - Extracted code from existing projects

Build

Install development dependencies in your git checkout:

$ npm install

~Build and run tests:

$ grunt

See the Gruntfile.js for additional commands.

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Note: this is an opinionated module: please create a ticket to discuss any big ideas. Pull requests for bug fixes are of course always welcome.

License

Copyright (c) 2013 Bart van der Schoor

Licensed under the MIT license.