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

@acryps/log

v0.0.0

Published

Log formatter

Downloads

115

Readme

Logger

Logs color coded messages to console.

D 2024-12-13T13:19:07 test-unit: i am a debug message
L 2024-12-13T13:19:08 test-unit: i am a log message
W 2024-12-13T13:19:09 test-unit: i am a warn message
E 2024-12-13T13:19:10 test-unit: i am a error message
const importerLogger = new Logger('Importer');

for (let article of articles) {
	const logger = importerLogger.child(article.id);

	if (article.image != newImage) {
		logger.log('updated image', newImage.hash);
	}
}

Each unit gets a consistent color, based on its name.

Child Units

Branch into child logging units using the .task(name: string) or .child(name: string). This will show both the parents and the child units name in the log output

Tasks can be finished using .finish(...messages).

Accessory

A unit can have an accessory generator, which can add essential dynamic information to the logging output. This can for example be used to show a queue length.

const logger = new Logger('compressor');
const queue = new Queue();

logger.accessory = () => `${queue.length}q`;

queue.dispatch(async task => {
	async task.compress();

	logger.log('compressed', task.name, 'from', task.source.size, 'to', task.compressed.size);
});

for (let file of uploads) {
	queue.add(new CompressTask(file));
}
L 2024-12-13T13:19:00 compressor (10q): compressed hello-1.mp4 from 11123 to 4001
L 2024-12-13T13:19:00 compressor (9q): compressed hello-2.mp4 from 3123 to 512
L 2024-12-13T13:19:00 compressor (8q): compressed hello-3.mp4 from 44412 to 3251
L 2024-12-13T13:19:00 compressor (13q): compressed hello-4.mp4 from 13662 to 3111

This shows that new files must have been added to the queue betwen the 3. and 4. import.