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 🙏

© 2026 – Pkg Stats / Ryan Hefner

logicus

v0.0.10

Published

A multi-level log for your html application!

Downloads

6

Readme

Logicus

A multi-level log for your html applications!

How to use it:

  • Import the css in your files
  • create a new Logicus item on application start (see the configuration section)
  • use logicus.log / .warn /.error instead of your console.log / .warn / .error to let it override the console!
  • (optional) set a linting rule to ensure you are not using console.log anywhere

How to configure it:

Logicus accepts three parameters, the first of which is required:

  • logLevels: an array of LogLevels. These are needed to define the log types you want to use. Log levels are structured as follows:
    name: string;
    id: T;
    associatedEmoji?: string;
    color: [number, number, number];
    logImportance: number;
    }
  • DisplayAll: a boolean stating if the logs must be shown. Default: true
  • KeyCombination: a combination of keys needed to trigger the console. It is structured as follows:
      shift?: boolean;
      alt?: boolean;
      ctrl?: boolean;
      key: string;
    }

How to test it:

npm run example then open a browser on port 3000

  • You'll see 3 buttons, each will log something
  • By pressing CTRL + L you can toggle the log filter, have fun!