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

ologg

v1.2.0

Published

Simple logger.

Downloads

8

Readme

Ologg

Simple node.js logger.

Installation

npm install ologg

Getting started

const Ologg = require('ologg');
const logg = new Ologg({
	outputFile: true, //Should entries be output to file.
	outputConsole: true, //Should entries be output to console.
	singleFile: '/path/to/log/file', //If you want to output to a single file, set it here.
	folder: '/path/to/folder', //Path to the folder that the logs will be saved.
				//By default logs are separated by date.
	includeTime: true //Should timestamp be added to entries.
})
//If single file and folder are set, Ologg will use the single file.
//Not all settings are required, but either singleFile or Folder are required.

Ologg.info(message)

const logg = new Ologg({
   folder: '/path/to/folder'
});

logg.info('Test!');
logg.info('Hello!!!');
logg.info('World!!!');

This will output:

[00:07:48][INFO]: Test!
[00:07:48][INFO]: Hello!!!
[00:07:48][INFO]: World!!!

Ologg.error(message)

Just like info but error adds spacing to make error entries more visible.

const logg = new Ologg({
   folder: '/path/to/folder'
});

logg.info('test');
logg.info('test');
logg.error('OH NOES!'); //<= ERROR ENTY
logg.info('info');
logg.info('entry');
logg.error('THERE WAS AN ERROR!!!'); //<= ERROR ENTY
logg.info('test');
logg.info('test');

This will output:

[00:09:37][INFO]: test
[00:09:37][INFO]: test

[00:09:37][ERROR]: OH NOES!

[00:09:37][INFO]: info
[00:09:37][INFO]: entry

[00:09:37][ERROR]: THERE WAS AN ERROR!!!

[00:09:37][INFO]: test
[00:09:37][INFO]: test

Ologg.log(message, type, format)

const logg = new Ologg({
   folder: '/path/to/folder'
});

logg.log('Testing this', 'TEST');
logg.log('Testing notype');
logg.log('Testing haha', 'INFO', false);

This will output:

[16:21:30][TEST]: Testing this
[16:21:30]: Testing notype
Testing haha

Ologg.setOutputConsole(bool)

Should ologg output to console too.

logg.setOutputConsole(false) //Ologg will now not output to console too.

Ologg.setIncludeTime(bool)

Should ologg output to console too.

logg.setIncludeTime(false) //Ologg will now not include a timestamp in every entry.