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

@hmcts/nodejs-logging

v4.0.4

Published

[![Greenkeeper badge](https://badges.greenkeeper.io/hmcts/nodejs-logging.svg)](https://greenkeeper.io/)

Downloads

25,356

Readme

Node.js Logging

Greenkeeper badge

A logging component used by Reform's Node.js applications.

This is not compatible with Reform tactical logging spec. Logger 2.x should be used for tactical applications.

Some background info:

  • there are 6 log levels: silly (5), debug (4), verbose (3), info (2), warn (1) and error (0).
  • log level can be set via an environment variable LOG_LEVEL, the default is info.
  • logging output in JSON format can be enabled by setting environment variable JSON_PRINT to true, the default is false:
  • by default logging is turned off when running the unit tests.

Usage

Add it as your project's dependency:

yarn add @hmcts/nodejs-logging

Require it:

const { Logger } = require('@hmcts/nodejs-logging')

Then you can create a logger instance and use it to log information:

const logger = Logger.getLogger('app.js') // app.js is just an example, can be anything that's meaningful to you

Usage are:

logger.info({
  message: 'Yay, logging!'
})

or

logger.log({
  level: 'info',
  message: 'What time is the testing at?'
});

Above will result in the following log printed (if JSON format is enabled).

{ level: 'info',
  message: 'What time is the testing at?',
  label: 'app.js',
  timestamp: '2017-09-30T03:57:26.875Z' }

Access logging for Express applications

Optionally you can use the built-in Express access logger:

const { Express } = require('@hmcts/nodejs-logging')

app.use(Express.accessLogger())

Units Tests

Just do

yarn test

License

This project is licensed under the MIT License - see the LICENSE file for details.