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

@erdc-itl/simple-logger

v1.1.0

Published

A simple logger

Readme

Simple Logger

Installation

npm install @erdc-itl/simple-logger

Usage

var Logger = require("simple-logger");
var trainingLog = new Logger("training");
var reportLog = new Logger("reporting");

trainingLog.verbose("Hello!");
trainingLog.info("Information");
reportLog.warn("WARNING!");
reportLog.error("IT ALL BROKE!!!");

The only argument to the Logger constructor is the name applied in log messages. You can create multiple loggers within your app to distinguish different parts of the app from each other.

The above code will result in a log that looks something like this:

[5 May 2015 14:32:00] 📢 verbose training Hello!
[5 May 2015 14:32:01] ℹ️ info training Information!
[5 May 2015 14:32:02] ⚠️ warn reporting WARNING!
[5 May 2015 14:32:03] ⛔️ error reporting IT ALL BROKE!

Except it'll be colorful.

Configuration

The logger has some simple options that can be set globally, including the log level, output files, and log rotation options.

var Logger = require("simple-logger");
Logger.setOptions({
	level: 10,
	console: true,
	files: [ "/logs/my.log" ],
	rotate:  1024
});

The options are:

|Name|Description| |---|---| |level|The level is a number that determines the minimum log messages to output. The levels are 10 (verbose), 20 (info), 30 (warning) and 40 (error). Defaults to info.| |console|Boolean indicating whether to write the log to the console. Defaults to true.| |files|Array of string paths to write the log to. If any of the paths don't exist, they will be created. Defaults to no file.| |rotate|File size, in bytes, at which to rotate the log. When the log file exceeds this size, it is compressed and renamed, and a new log file created. 0 will disable rotate. Defaults to 0.|