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

esrol-logger

v1.0.2

Published

Write different type of messages, create daily log files and output colored messages to the console.

Downloads

5

Readme

NPM version Build Status Test coverage

esrol-logger

Write different type of messages, create daily log files and output colored messages to the console.

Part of Esrol

Installation

$ npm install --save esrol-logger

Node Version Compatibility

| Node Version | | ---- | | >= 4.x |

Examples

'use strict';
let Logger = require('esrol-logger');
let logger = new Logger('your-namespace');

// The following will write messages into log file
// You can use LOGGER_TYPES=* node dummy.js or LOGGER_TYPES=info,error node dummy.js
// to output message into console
logger.warning('w', 'Warning message');
logger.alert('a', 'Alert message');
logger.error('e', 'Error message');
logger.critical('c', 'Critical message');
logger.info('i', 'Info message');
logger.notice('n', 'Notice message');
logger.success('s', 'Success message');
logger.badrequest('b', 'Badrequest message');
logger.unauthorized('login', {username: 'dummy', password: 'qwerty123'});
// The debug behave just like node debug module
// and you should use the DEBUG variable
// DEBUG=your-namespace node dummy.js or DEBUG=* node dummy.js
// Note: the debug method does not write message into log file
logger.debug('Debug message');
// Or you can combine all of them like:
// DEBUG=* LOGGER_TYPES=* node dummy.js
// ENJOY THE RAINBOW :D

Logger

Methods

static method setLogDir(directory)

set logs directory

| Param | Type | Description | | --- | --- | --- | | directory | string | abs path to the folder |

alert(kind, message) ⇒ string

Alert message, yellow color

Returns: string - message - formatted message

| Param | Type | Description | | --- | --- | --- | | kind | string | additional info about the operation | | message | mixed | the message to be written |

critical(kind, message) ⇒ string

Critical message, red color

Returns: string - message - formatted message

| Param | Type | Description | | --- | --- | --- | | kind | string | additional info about the operation | | message | mixed | the message to be written |

error(kind, message) ⇒ string

Error message, red color

Returns: string - message - formatted message

| Param | Type | Description | | --- | --- | --- | | kind | string | additional info about the operation | | message | mixed | the message to be written |

warning(kind, message) ⇒ string

Warning message, yellow color

Returns: string - message - formatted message

| Param | Type | Description | | --- | --- | --- | | kind | string | additional info about the operation | | message | mixed | the message to be written |

notice(kind, message) ⇒ string

Notice message, cyan color

Returns: string - message - formatted message

| Param | Type | Description | | --- | --- | --- | | kind | string | additional info about the operation | | message | mixed | the message to be written |

info(kind, message) ⇒ string

Info message, cyan color

Returns: string - message - formatted message

| Param | Type | Description | | --- | --- | --- | | kind | string | additional info about the operation | | message | mixed | the message to be written |

success(kind, message) ⇒ string

Success message, green color

Returns: string - message - formatted message

| Param | Type | Description | | --- | --- | --- | | kind | string | additional info about the operation | | message | mixed | the message to be written |

unauthorized(kind, message) ⇒ string

Unauthorized message, yellow color

Returns: string - message - formatted message

| Param | Type | Description | | --- | --- | --- | | kind | string | additional info about the operation | | message | mixed | the message to be written |

badrequest(kind, message) ⇒ string

Badrequest message, white color

Returns: string - message - formatted message

| Param | Type | Description | | --- | --- | --- | | kind | string | additional info about the operation | | message | mixed | the message to be written |

Note

If NODE_ENV=production the message will not be shown in the console

Tests

To run the test suite, first install the dependencies, then run npm test:

$ npm install
$ npm test

License

MIT