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

nocms-logger

v4.2.3

Published

Logger package for NoCMS services

Downloads

93

Readme

Logger package for NoCMS

semantic-release Dependency Status devDependencies

Install

npm install nocms-logger

Usage

const logger = require('nocms-logger');
logger.warn(<message or object goes here>);

Config

Use logger.setConfig(configObj) to override the defaults.

| field | description | default | |-----------------|--------------------------------------------------------------------------|-------------| | logLevel | One of debug, info, warn or error, or numeric, 1-4. Select the minimun log level to to output | debug | | timestampFormat | strftime formatted date string. Example '%d.%m.%Y %H:%M' | ISO 8601 | | logFormat | String template for log format. %T for timestamp, %C for message content and %L for numeric log level | '%T %L %C' | | output | One of console, none or file. The logger functions return the output string, so that ouput none makes sense if you wish to manually do the logging using the returned value. Output file uses an additional outputConfig object. | console | | outputConfig | One output config can be assigned for each log level, in addition to all which will cover all of them. Each config is an object with a property file pointing to a file, of which the log entry is appended to. |   | | serializers | An object containing a set of functions to serialize certain types of log entries. The logger functions takes a second parameter, serializer, which will match a serializer provided in the config.

Output Config Example

This example shows the configuration where all log entries are logged to file (file.log), whereas debug entries are also logged to console, info entries to info.log and errors to error.log. Each log level can also have an array lising multiple log outputs, such as error in the following example.

config.output = {
  all: { file: '/path/to/file.log' },
  debug: 'console',
  info: { file: '/path/to/info.log' },
  error: ['console', { file: '/path/to/error.log' }],
};

Serializer Example

This example shows how certain objects can be serialized to custom formatted strings. Keep in mind that it is only the entry's content (%C) that is serialized, so that you can use the logFormat configuration as well.

config.serializers = {
  superagentError: (err) => {
    return `${err.status} ${err.response.text}`;
  }
};

Further specifying log format logFormat: '%C (%L)' will result in the following output: 404 Not found (4).