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 🙏

© 2025 – Pkg Stats / Ryan Hefner

testitttt

v22.0.0

Published

A wrapper utility for Winston

Readme

ps-chronicle

A logger package which is PS specific and uses winston internally. It is used to create logs in 2 formats -> JSON or Simple. The default format is JSON. The log levels allowed are : error, wspayload, info, warn, debug. The timezone is GMT

installation

npm i ps-chronicle

usage

Step 1) Import/require package

const Logger = require('ps-chronicle');

Step 2) Initialize your logger - once per file/class inside your lambda handler . All three fields are optional If outputFormat is not given then the default format will be "json", If loglevel is not set during initialization, then by default it will "debug"

var outputFormat = 'json' or 'simple'
var logger = new Logger('example.js', 'json', 'info'); // (fileName, outputFormat, logLevel)

Step 3) Set requestID per lambda. This request id can be obtained from context object of the lambda. For more information please visit https://docs.aws.amazon.com/lambda/latest/dg/nodejs-context.html Please set request Id as the format ==> LoggerClassName.setRequestId(context.awsRequestId);

Logger.setRequestId(context.awsRequestId); // ClassName.methodName as it is a static method

Step 4) Set customer name per lambda.

Logger.setCustomerName('RSA'); // ClassName.methodName as it is a static method

Step 5) Also, set method name for each method.

logger.setMethodName('testMethod()');

Step 6) If the log level defined in the log() function is not in the scope then the default log level ,i.e info is set. log() function parameters : i. log level ii. message iii. after above two parameters, n number of parameters can be given. All will be the part of key: additionalinfo , which is an array.

function sum(a, b) {
	logger.setMethodName('sum()');
	logger.log('INFO', ' testing  info logger ');
	logger.log('silly', 'testing silly logger '); //silly is not in scope so default log level is set -> info

	logger.log(
		'error',
		' testing error logger ',
		{ tags: 'HEADERS', headers: event.headers },
		{ tags: 'BODY', body: event.body }
	);
	logger.log(
		'wspayload',
		'testing simple wspayload logger ',
		{ tags: 'HEADERS', headers: event.headers },
		{ tags: 'BODY', body: event.body }
	);
	logger.log(
		'warn',
		'testing simple warn logger ',
		{ tags: 'HEADERS', headers: event.headers },
		{ tags: 'BODY', body: event.body }
	);
	logger.log(
		'debug',
		'testing simple debug logger ',
		{ tags: 'HEADERS', headers: event.headers },
		{ tags: 'BODY', body: event.body }
	);
	//rest of the code
}

Important : If loggers are not getting printed for async functions then please use the below code at the end of your lambda function:

await logger.waitForLogger(Logger);
`