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

@reagent/logging

v0.1.0

Published

Standardized application logging with winston

Downloads

6

Readme

Logging

A winston-based logger with standardized JSON and plaintext formatting.

Installation

Install from NPM:

$ yarn add @reagent/logging

Usage

The logger supports all the common syslog levels. To create your logger use the createLogger() helper function and make sure you emit to either stdout or a filePath (or both):

import path from 'path';
import { createLogger } from '@reagent/logger';

const stdoutLogger = createLogger({ stdout: true });
stdoutLogger.info('Message to stdout'); // Will emit a message at `info` level to your console

const fileLogger = createLogger({
  filePath: path.resolve(__dirname, 'log', 'messages.log'),
});
fileLogger.info('Message to file'); // Will emit a message at `info` level to the target file

The logger is configured to emit logs at 'info' level, but this can be modified as needed:

const { NODE_ENV } = process.env;

const logger = createLogger({
  stdout: true,
  level: NODE_ENV === 'production' ? 'warning' : 'info',
});

logger.info('Informational message'); // Not emitted in 'production'
logger.warning('Warning message');

By default, logs are formatted as plaintext, but you can format as json as well:

const plainLogger = createLogger({ stdout: true });
plainLogger.info('Message in Plain');
// [2023-02-11T17:12:06.459Z] (info): Message in Plain

const jsonLogger = createLogger({ stdout: true, format: 'json' });
jsonLogger.info('Message in JSON');
// {"level":"info","message":"Message in JSON","timestamp":"2023-02-11T17:12:06.461Z"}

You can also provide a source and any additional information to the log messages. The use of generics supports constraints and type inference for the source attribute:

const logger = createLogger<'app' | 'db'>({ stdout: true });
logger.info('Message from application', { source: 'app' });
// [2023-02-11T17:15:37.260Z] (info): Message from application source=app

logger.info('Message from database', { source: 'db' });
// [2023-02-11T17:16:33.715Z] (info): Message from database source=db

logger.info('Message from application with extra', {
  source: 'app',
  request: { path: '/user' },
});
// [2023-02-11T17:15:37.262Z] (info): Message from application with extra source=app request={"path":"/user"}

As in previous examples, emitting the logs as json is also possible.