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

@ovotech/winston-logger

v1.2.6

Published

Winston logger wrapper

Downloads

345

Readme

Winston logger

Wrap winston logger to hide graylog semantics and implement safe static meta contexts.

Using

yarn add @ovotech/winston-logger
import { Logger } from '@ovotech/winston-logger';
import * as winston from 'winston';

const winstonLogger = winston.createLogger(...);

const myRequestProcessor = (req: Request) =>{
  const logger = new Logger(winstonLogger, { traceToken: req.headers['X-Trace-Token'] });

  logger.info('test');
}

All the normal winston logger methods are implemented, alongside their "log('level', ...)" counterparts.

logger.silly('test-message', { other: 'stuff' });
logger.log('silly', 'test-message', { other: 'stuff' });

logger.notice('test-message', { other: 'stuff' });
logger.log('notice', 'test-message', { other: 'stuff' });

logger.info('test-message', { other: 'stuff' });
logger.log('info', 'test-message', { other: 'stuff' });

logger.warn('test-message', { other: 'stuff' });
logger.log('warn', 'test-message', { other: 'stuff' });

logger.error('test-message', { other: 'stuff' });
logger.log('error', 'test-message', { other: 'stuff' });

Adding static meta

You can add more static meta after the class has been instantiated. This however results in a new Logger with the additional (merged) static meta, and the old object is unaffected.

import { Logger } from '@ovotech/winston-logger';
import * as winston from 'winston';

const winstonLogger = winston.createLogger(...);

const logger = new Logger(winstonLogger, { uri: '/some-url' });
const extendedLogger = logger.withStaticMeta({ additional: 'test' });

Sanitizers

You can add functions that modify the metadata just before the log is sent. This is use to redact sensitive info from the log.

import { Logger, LoggerSanitizer } from '@ovotech/winston-logger';
import * as winston from 'winston';

const winstonLogger = winston.createLogger(...);

const sanitize: LoggerSanitizer = (meta) => {
  const { email, ...rest } = meta;
  return rest;
}

const logger = new Logger(winstonLogger, {}, [sanitize]);
logger.info("User logged in", { email: '[email protected]' });

You can add additional sanitizers later on with the withSanitizers method, it will not modify the logger instance, but create a new one, with the additional sanitizers.

Running the tests

Then you can run the tests with:

yarn test

Coding style (linting, etc) tests

Style is maintained with prettier and tslint

yarn lint

Deployment

Deployment is preferment by lerna automatically on merge / push to master, but you'll need to bump the package version numbers yourself. Only updated packages with newer versions will be pushed to the npm registry.

Contributing

Have a bug? File an issue with a simple example that reproduces this so we can take a look & confirm.

Want to make a change? Submit a PR, explain why it's useful, and make sure you've updated the docs (this file) and the tests (see test folder).

License

This project is licensed under Apache 2 - see the LICENSE file for details