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

gudangjs

v1.2.1

Published

GudangJS - A simple and lightweight javascript Log service

Readme

GudangJS

A simple and lightweight javascript Log service.

How to get started?

Just import Log class, add some appenders at the start of your application, and then use it freely :)

    Log.info('Just saying that everything is going well :)');

    Log.warn('Something bad happened, but we handled well with that :D');

    Log.error('Hey, something bad happened :/');

Set Global LOG Level :

// Set log level to ERROR (only errors will be logged)
Log.level = LogLevel.ERROR;

Log.debug('This will not be logged');
Log.warn('This will not be logged too');
Log.error('This will be.');

Create custom formatters :

class JhonDoeFormatter implements LogFormatter {

    format(line: LogLine): string {
        return `Jhon Doe said: '${line.text}' When? At ${line.timestamp.toLocaleDateString()}. It was a ${line.level}.`
    }

}
// Don't forget to register the appender!
Log.setAppenders(new ConsoleLogAppender(new JhonDoeFormatter()));

Use Filesystem log appenders :

Log.addAppender(new FileSystemLogAppender('/var/log/my_app_log.log'));

// Create a rotating log on the file system
Log.setAppenders([
    new RotatingFileSystemLogAppender('/tmp/', 'system_logs')
]);

Log.error('This will be logged on the file system, in a file called system_logs_YYYY-MM-DD.txt');

Create custom appenders:

class JohnDoeAppender extends AbstractLogAppender {

    append(line: LogLine): void {
       console.log(`Jhon Doe said: '${line.text}'`);
    }

}
// Don't forget to add that to the logger!
Log.addAppender(new JohnDoeAppender());

Use multiple appenders :

Log.setAppenders([
    new ConsoleLogAppender(),
    new FileSystemLogAppender('/tmp/my_log.txt')
]);

Feel free to request for improvements or open issues for bugs :D