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

dalog

v1.0.2

Published

Simple logger for node.js

Downloads

2

Readme

node-dalog

Simple Logger with spawning, source code and event tracing. ES6 compatible.

Usage

JS example:

var Logger = require('dalog').default;
logger = new Logger();
logger.log('Hello','world');

ES6 example:

import Logger from 'dalog';

export class MyApp {
  constructor {
    this.logger = new Logger();
    this.logger.log('Hello','world');
  }
}

This would log using console.log() and output something like:

[ead88891](app.js:3:8) Hello world

The format is as follows:

[$(id)]($(file):$(line):$(character)) $(message)

id: Random identificator to easily track source of evented log calls. Very useful when having many streams, log messages usually merge and mix, making traceability almost impossible.
file: Source file name that called the logger.
line: Line of source file in which the logger was called.
character: Position in line from which the logger was called.
message: Multiple arguments turned into string message, same as using console.

Console support

Logger is mounted over console, and supports .log(), .info(), .warn(), .error() and multiple arguments.

Spawning child loggers

It's possible to spawn the logger to trace specific events, for example:

var Logger = require('dalog').default;
appLogger = new Logger();
appLogger.log('Hello','world');

timerLogger = appLogger.spawn();
failLogger = appLogger.spawn();

setInterval(function() {
  timerLogger.info('Tick!', +new Date);
}, 1000);

setTimeout(function() {
  failLogger.error('Fail!');
  process.exit(1);
}, 5000);

It's similar to creating a new instance of the logger, but there are plans to trace back parent/children calls. Also date/time, format and other features on the bucketlist.

Output of example above:

[b3d3b328](app.js:3:11) Hello world
[3598caeb](app.js:9:15) Tick! 1661859488022
[3598caeb](app.js:9:15) Tick! 1661859489028
[3598caeb](app.js:9:15) Tick! 1661859490032
[3598caeb](app.js:9:15) Tick! 1661859491037
[4115b85d](app.js:13:14) Fail!

License

MIT