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

@gojob/winston-bugsnag

v0.1.0

Published

Winston Transporter for Bugsnag. Based on Niftylettuce's work (Nick Baugh).

Downloads

12

Readme

winston-bugsnag-logger

node bugsnag winston license

The maintained and well-documented Bugsnag transport for the winston logger.

Full API documentation is available at: https://docs.bugsnag.com/api/error-reporting/

Index

Install

npm install --save winston winston-bugsnag-logger

Usage

You can configure winston-bugsnag-logger in two different ways.

With new winston.Logger:

const winston = require('winston');
const Bugsnag = require('winston-bugsnag-logger');

const options = {
  apiKey: '*******',
  level: 'info'
};

const logger = new winston.Logger({
  transports: [
    new Bugsnag(options)
  ]
});

Or with winston's add method:

const winston = require('winston');
const Bugsnag = require('winston-bugsnag-logger');

const logger = new winston.Logger();

logger.add(Bugsnag, options);

See Options below for custom configuration.

Options (options)

Per options variable above, here are the default options provided:

Default options:

  • apiKey (String) - your Bugsnag API key (defaults to process.env.BUGSNAG_API_KEY)
  • config (Object) - a Bugsnag configuration object
  • bugsnag (Object) - an optional instance of bugsnag that is already configured via bugsnag.register (if provided this will be used instead of the config option)

Transport related options:

  • name (String) - transport's name (defaults to bugsnag)
  • silent (Boolean) - suppress logging (defaults to false)
  • level (String) - transport's level of messages to log (defaults to info)
  • levelsMap (Object) - log level mapping to Bugsnag (see Log Level Mapping below)

Log Level Mapping

Winston logging levels are mapped by default to Bugsnag's acceptable levels.

These defaults are set as `options.levelsMap' and are:

{
  silly: 'info',
  verbose: 'info',
  info: 'info',
  debug: 'debug',
  warn: 'warning',
  error: 'error'
}

You can customize how log levels are mapped using the levelsMap option:

new Bugsnag({
  levelsMap: {
    verbose: 'info'
  }
});

If no log level mapping was found for the given level passed, then it will not log anything.

License

MIT License