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 🙏

© 2024 – Pkg Stats / Ryan Hefner

basic-log

v0.1.2

Published

A simple logging library

Downloads

15

Readme

A simple logging library for Node.js

Installing

$ npm install basic-log

Basic usage

var log = require('basic-log');

log('Hello!');

Output:

2013-01-19 09:01:53.478 Hello!

log takes a single argument, converts it to string, and prints it to console.

Other log levels:

log.d('Hello!');
log.i('Hello!');
log.w('Hello!');
log.e('Hello!');

Output:

2013-01-19 09:03:17.671 [debug] Hello!
2013-01-19 09:03:17.671 [info] Hello!
2013-01-19 09:03:17.671 [warn] Hello!
2013-01-19 09:03:17.671 [error] Hello!

Changing the date format

By default, the date format is YYYY-MM-DD hh:mm:ss:mmm in UTC time.

Change it by setting date:

log.date = function() {
	return new Date().getTime() + ' ';
}

log('Hello!');

Output:

1358586277536 Hello!

Or get rid of the time altogether:

log.date = function() {
	return '';
}

log('Hello!');

Output:

Hello!

Changing the output

By default, messages are written using console.log.

Change it by setting output:

log.output = function(message) {
	console.err(message);
}

log('Hello!'); // prints to stderr

Or make it return a value if you like:

log.output = function(message) {
	return message.toUpperCase();
}

console.log(log('Hello!'));

Output:

HELLO!

Creating new instances

If want to avoid changing the global log, you make create a new instance:

var Log = require('basic-log').Log;
var log = new Log(<custom functions>);

A typical use case would be to create your own log module and use it:

lib/my-log.js:

var Log = require('basic-log').Log;

module.exports = new Log({
	date: function() { return new Date().getTime() + ' '; }
});

my-app.js:

var log = require('./lib/my-log');

log('Hi!');