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/de-collide-console

v1.0.0

Published

manage stdout and stderr so that they do not collide in the console

Downloads

1

Readme

de-collide-console

Motivation

Console MUX to marshal stdout and stderr to work around a bug in Webstorm. Because the two streams are not coordinated this happens...

image

Method

The two output streams are hooked and all transmissions are wrapped in promises to write after a fixed delay. The promises are chained to maintain the order of the transmissions. The module exports a constructor that takes an argument which is the delay between transmissions in milliseconds. The queue will expand as required and a drain event will be emitted after the last member has been sent. Because the writes are asynchronous, the drain event needs to be used to unhook after all writes are completed, otherwise there would be collisions as the queue empties after being unhooked.

A timeout is provided in the unlikely event that the the streams hang. If this happens an error event will fire which the consumer can chose to handle. Similarly, if there is a stream error the remaining queue will be skipped and the error reported to the consumer.

Just add the following code...

var Decollide = require('de-collide-console');

new Decollide(10);
Decollide.on('drain' ,() => {
  Decollide.unhook();
});

The collisions are removed...

image