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

node-app-logger

v1.0.7

Published

structured logging for node.js applications

Downloads

10

Readme

Structured logging with request context

Install

# using npm
npm install node-app-logger
 
# using yarn
yarn add node-app-logger

Usage

# using require
const { Correlation, Logger } = require('node-app-logger');
 
# using import
import { Correlation, Logger } from 'node-app-logger';

Example

Without correlation

import { Logger } from 'node-app-logger';

const LOG_DIR = './.logs';
const LOG_FILE_PREFIX = 'my_app';

const logger = new Logger(LOG_DIR_NAME, LOG_FILE_PREFIX);

# info log
logger.info('info message', ['TEST', 'INFO']);

# error log
const error = new Error('Test Error');
logger.error('error message', error, ['TEST', 'ERROR']);

# debug log
# for debug log, "process.env.LOG_LEVEL = 'debug';" is required, default is 'info'.
logger.debug('debug message', ['TEST', 'DEBUG']);

# warn log
logger.warn('warn message', ['TEST,' 'WARN']);

With correlation

import express from 'express';
import { Correlation, Logger } from 'node-app-logger';

const app = express();

const LOG_DIR = './.logs';
const LOG_FILE_PREFIX = 'my_app';

const logger = new Logger(LOG_DIR, LOG_FILE_PREFIX);

// Set the Correlation middleware for collecting http request information
app.use(Correlation.setData);

app.get('/api/v1/user/1', (req: any, res: any, next: any) => {
    const customerId = '123';
    Correlation.updateCustomerId(customerId);
    logger.info('info message', ['USER', 'API']);
    res.send(200);
});

app.listen(3000, () => {
    logger.info('App is listening on port 3000', ['APP']);
});

A new file will be created under the specified dir with the following content including customer id and other http request information.

{"@timestamp":"2022-04-24T08:12:24.038Z","customerId":"","fileName":"","host":"197NODMB27479.local","level":"info","message":"App is listening on port 3000","pid":49970,"request":{"method":"","normalizedUrl":"","remoteAddress":"","url":""},"requestId":"","tags":["APP"]}

{"@timestamp":"2022-04-24T08:12:29.026Z","customerId":"123","fileName":"","host":"197NODMB27479.local","level":"info","message":"info message","pid":49970,"request":{"method":"GET","normalizedUrl":"","remoteAddress":"::1","url":"/api/v1/user/1"},"requestId":"6539df3b-bcbb-4209-afb9-600781dcdb38","tags":["USER","API"]}

Note

When "NODE_ENV !== production" the logs will be printed to the console and file.
When "NODE_ENV === production" the logs will be printed to the file only.