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

node-logger-tool

v1.0.2

Published

Simple logging tool

Downloads

9

Readme

Config module

Simple module for logging. It is a standalone piece of code that does not require any other node modules.

Installation

In your project folder run:

npm install --save node-logger-tool

Note: The module code uses few ES6 features, so at least 4.4.5 version of Node is required.

Usage

First you need to include the module and configure it.

> const loggerFactory = require('node-logger-tool').create;
> const LoggerMode = require('node-logger-tool').LoggerMode;
>
> const logger = loggerFactory(LoggerMode.Console);

Requiring the module and using a create function that can be called with an argument to set logger output. If the factory parameter is ommited, it defaults to console. Sometimes it comes handy to log events in process.stdout or process.stderr rather than in console (see example). In that case, use LoggerMode.Stdio as an argument for factory function.

Using the logger module is quite straightforward:

logger.log('hello'); // outputs info: hello

logger.log(42, 'the number'); // outputs the number: 42 (providing the label for logged data)

logger.info('informed'); // same as logger.log()

logger.error(new Error('everything is lost')); // outputs error: everything is lost

If the non-primitive value like Array or Object is passed to the logger, it is JSON-encoded for better readability.

Logging to file requires more configuration (passing additional parameter to the loggerFactory function or setMode method).

const logger = loggerFactory(LoggerMode.File, 'path/to/folder');

logger.setMode(LoggerMode.File, 'path/to/folder');

Example

// parent.js
const log = require('node-logger-tool').create();   // defaults to console 
const spawn = require('child_process').spawn;
const child = spawn('node', ['child.js']);

child.stdout.on('data', (status) => {
    log.info('child process status: ' + status);
});
// child.js
const LoggerMode = require('node-logger-tool').LoggerMode; 
const logger = require('node-logger-tool').create(LoggerMode.Stdio)';
const notify = logger.info.bind(logger);

// do some heavy lifting...

// notify the parent process
notify('work done');

Issues

Since the GitHub repository is not ready yet, please use my email address in profile to contact me. Cheers!