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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@commercetools-backend/loggers

v25.2.0

Published

Opinionated JSON loggers for HTTP server applications

Readme

@commercetools-backend/loggers

Opinionated JSON loggers for HTTP server applications.

Install

$ npm install --save @commercetools-backend/loggers

Middlewares

Access logger

Creates a logger to be used for HTTP requests access logs.

const {
  createAccessLoggerMiddleware,
} = require('@commercetools-backend/loggers');

app.use(createAccessLoggerMiddleware());

Options

  • level (string): The log level to be used. Default: info
  • silent (boolean): In case logs should be skipped. Default: false
  • json (boolean): To use the JSON formatter, otherwise falls back to CLI format. It's recommended to use the JSON formatter on production.
  • formatters (Array of Winston formatters): In case you want to pass additional Winston formatters.
  • ignoreUrls (Array of string): A list of URL paths to be ignored from being logged.

Application logger

Creates a logger to be used programmatically in the application code.

const { createApplicationLogger } = require('@commercetools-backend/loggers');

const app = createApplicationLogger();

app.info('Hey there', { meta: { name: 'Tom' } });

Options

  • level (string): The log level to be used. Default: info
  • silent (boolean): In case logs should be skipped. Default: false
  • json (boolean): To use the JSON formatter, otherwise falls back to CLI format. It's recommended to use the JSON formatter on production.
  • formatters (Array of Winston formatters): In case you want to pass additional Winston formatters.

Formatters

The package provides some come Winston formatters that can be passed to the given loggers.

Rewrite fields

This formatter allows to rewrite fields from the JSON logger. It can be useful for redacting insecure information, or to map certain fields to a specific format (for example for Kibana).

const {
  createAccessLoggerMiddleware,
  rewriteFieldsFormatter,
} = require('@commercetools-backend/loggers');

app.use(
  createAccessLoggerMiddleware({
    formatters: [
      rewriteFieldsFormatter({
        fields: [
          { from: 'level', to: 'logLevel' },
          { from: 'meta.error.message', to: 'meta.errorMessage' },
          {
            from: 'meta.error',
            to: 'meta.errorJsonString',
            replaceValue: (value) => JSON.stringify(value),
          },
        ],
      }),
    ],
  })
);

Options

  • fields (Array of RewriteField): A RewriteField is an object with the following properties:
    • from (string): A JSON path to one of the fields of the log information that needs to be rewritten. The field will be deleted.
    • to (string): A JSON path to the new field that should be created.
    • replaceValue (function): An optional function that takes the value from the original field and returns a new value for the field. It can be used for example to serialize the value with JSON.stringify.