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

s-logger

v2.0.1

Published

A simple logger with DEBUG state and light customization

Downloads

5

Readme

s-logger

A simple log with DEBUG state and light customization

npm i s-logger --save

Basic usage:

var log = require('s-logger');

log.DEBUG = true; // default false, but inherit previos changes

log( 'log', 'any', 'count', 1,2,3,4, { and: 'any type', of: ['data'] } );

Note: DEBUG you can change any time. But it was conceived as a response to the setting when initializing the application in the states DEBUG = true/false. This means that after the change log flag ceases to work in all parts of the application.

Note: since version 1.1.2 adds the ability to change the color scheme of shortcut.

Colors: black, red, green, yellow, blue, magenta, cyan, white, grey.

Customization:

// complete detailed configuration
var config = {
	DEBUG: true,
	CUSTOM: {
		text: 'custom-CUSTOM',
		background: 'black',
		color: 'grey',
		log: function ( arrayOfArguments ) { // only for custom
			for ( var key = 0; key < arrayOfArguments.length; key ++ ) {
				console.log( arrayOfArguments[ key ] );
			}
		}
	},
	ERROR: {
		text: 'custom-ERROR',
		background: 'red',
		color: 'white',
	},
	WARN: {
		text: 'custom-WARN',
		background: 'green',
		color: 'cyan',
	},
	INFO: {
		text: 'custom-INFO',
		background: 'yellow',
		color: 'magenta',
	},
	LOG: {
		text: 'custom-LOG',
		background: 'blue',
		color: 'red',
	}
};

var log = require('s-logger');

var customLog = log.create( 'uniqueIdOfLogger-hash-care', config );


// default false, but inherit previos changes
log.DEBUG
customLog.DEBUG // It does not intersect with the other loggers

// Can be another file (connected later)
if ( customLog === ( require('s-logger') ).get('uniqueIdOfLogger-hash-care') ) {
	customLog( 'Completely usability victory !!!' );
} else {
	log( 'Completely fail ...' );
}

Note: Delegation to other files is due to mapping inside

Example out in chrome devtool:

log( 'log', 'log.DEBUG = true', 'any', 'count', 1,2,3,4, { and: 'any type', of: ['data'] } );
// S-LOG:
//	log.DEBUG = true any count 1 2 3 4 Object {and: "any type", of: Array[1]}

log( 'info', 'log.DEBUG = true', 'any', 'count', 1,2,3,4, { and: 'any type', of: ['data'] } );
// S-INFO:
//	log.DEBUG = true any count 1 2 3 4 Object {and: "any type", of: Array[1]}

log( 'warn', 'log.DEBUG = true', 'any', 'count', 1,2,3,4, { and: 'any type', of: ['data'] } );
// S-WARN:
//	log.DEBUG = true any count 1 2 3 4 Object {and: "any type", of: Array[1]}

log( 'error', 'log.DEBUG = true', 'any', 'count', 1,2,3,4, { and: 'any type', of: ['data'] } );
// S-ERROR:
//	log.DEBUG = true any count 1 2 3 4 Object {and: "any type", of: Array[1]}

Example out in cmd:

log( 'log', 'log.DEBUG = true', 'any', 'count', 1,2,3,4, { and: 'any type', of: ['data'] } );
// S-LOG:
//	log.DEBUG = true any count 1 2 3 4 Object {and: "any type", of: Array[1]}

log( 'info', 'log.DEBUG = true', 'any', 'count', 1,2,3,4, { and: 'any type', of: ['data'] } );
// S-INFO:
//	log.DEBUG = true any count 1 2 3 4 Object {and: "any type", of: Array[1]}

log( 'warn', 'log.DEBUG = true', 'any', 'count', 1,2,3,4, { and: 'any type', of: ['data'] } );
// S-WARN:
//	log.DEBUG = true any count 1 2 3 4 Object {and: "any type", of: Array[1]}

log( 'error', 'log.DEBUG = true', 'any', 'count', 1,2,3,4, { and: 'any type', of: ['data'] } );
// S-ERROR:
//	log.DEBUG = true any count 1 2 3 4 Object {and: "any type", of: Array[1]}

It would be interesting to know how you make out your logs.

As usual i make out of my log

log('custom',
	'log.DEBUG:', log.DEBUG,
	'simple action result:', 'BEST'.toLowerCase(),
	'some Object:', { and: 'any type', of: ['data'], 1: 1 },
	'some Array:', [1,2,3,'some other']
);
/* S

	log.DEBUG: true
	
	simple action result: best
	
	some Object: Object { '1': 1, and: 'any type', of: [ 'data' ] }
	
	some Array: [ 1, 2, 3, 'some other' ]
*/