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

log4ui

v0.1.7

Published

Logger implemented especially to run in browser

Readme

log4ui

npm version Build Status Coverage Status Gitter

Motivation

During development and debugging naturally we are adding a lot of logs of different levels, but native console object is not so granular. In other words you do not have any categories, labels or some other identifier which allows to enable logs for some module and disable them for other one.

Key features

  • Categories - split your logs by categories to see only what needed.
  • Runtime configuration - all your configuration could be changed in runtime. This allows to enable logs for some category based on some condition ot using browser console.
  • Persistence of configuration - your configuration is persisted using StoreAdapter(localStorage by default). This allows to you to create personalized configuration without changing source code at all(for example using browser console).