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

@selesterkft/express-logger

v1.2.0

Published

Logger for ExpressJS using winston

Downloads

16

Readme

@selesterkft/express-logger

Simple wrapper for winston and morgan for use in Express webapps.

Installation

Install the package with yarn:

yarn add @selesterkft/express-logger

Usage

This package supports three levels of logging, in descending order of severity:

  • logger.error()
  • logger.info()
  • logger.debug()

All of them are called with a single parameter which can be a simple string or a javascript object. Objects will be parsed to JSON. Log files will have a basic format: a JSON entry of any logging event per line.

For logging http calls, use logger.middleware() as an Express middleware.

import express from 'express';
import logger from '@selesterkft/express-logger';

const app = express();
// Note that we do call the middleware() function.
app.use(logger.middleware());

const PORT = 4000;

app.get('/', (req, res) => {
  res.send('Hello world!');
});

app.listen(PORT, () => {
  logger.info(`App is listening on ${PORT}.`);
});
import logger from '@selesterkft/express-logger';

export default function doSomething() {
  logger.error('Something was done!');
}

For logging request and response bodies (only meaningful in debug mode), use logger.bodyMiddleware() as a middleware. Do not call it, and make sure to use it after parsing the request body.

// ...
app.use(express.json());
app.use(logger.middleware());
app.use(logger.bodyMiddleware);
// ...

Log files

Log files will be written to the logs/ folder, so don't forget to add it to your .gitignore file.

# Logs
logs/

Console logging

Express-logger will read NODE_ENV to determine the current node environment, and, unless it is 'production' or 'test', will output the logs to the console. Be sure to set the node environment to 'production' when appropriate to suppress console logging.

Using Jest, for example, should automatically set the environment to 'test'.