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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@gimmick/terminal

v0.0.1

Published

A more robust consoling system making it easier to identify issues on your domain.

Readme

terminal

A more robust consoling system making it easier to identify issues on your domain.

About

The terminal is a direct copy of the console. With a few additions. The four main logging functions (log, info, warn, and error) are replaced with a new handler. This handler adds a prefix and performs some coloration.

Notes

  • Coloring in the console is only supported by modern browsers.
  • There is currently no way to surpress coloring.

Resources

| Variable | Type | Purpose | |-------------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| | terminal.suppress | Boolean | Controls whether log, info, warn, or error will output. | | terminal.prefix | String | A string prefixed to the start of every console output. | | terminal.styles | Object | Indexed by the type of function (log, info, warn, error) containing an array of two schemes for string coloration. First is for the prefix, second is your output. |

Examples


terminal.prefix = '[Nemo]';

// Will output, in dark blue, as [Nemo] Mount Wannahockaloogi...
terminal.info('Mount Wannahockaloogi...');

// Will output, in dark orange, as [Nemo] You get back here. RIGHT. NOW!
terminal.warn('You get back here. RIGHT. NOW!');

// Will output, in dark red, bold, as [Nemo] He touched the butt...
terminal.error('He touched the butt...');