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

logtify-bugsnag

v1.1.1

Published

Bugsnag link chain and adapter for logtify logger

Downloads

2

Readme

logtify-bugsnag

Sonar Sonar Sonar Sonar Sonar Sonar

Bugsnag execution subscriber for logtify logger

Installation

npm i -S logtify-bugsnag

Usage

Used with logtify module.

require('logtify-bugsnag')({ BUGS_TOKEN: 'YOUR_BUGSNAG_TOKEN' });
const { notifier } = require('logtify')();

notifier.notify(new Error('Test error'));
notifier.notify('Hello world!');

BEWARE!!

// if required after subscriber, adapter will be undefined
let { notifier } = require('logtify')();
require('logtify-bugsnag')({ BUGS_TOKEN: 'YOUR_BUGSNAG_TOKEN' });
// notifier is undefined

// So, you need to refresh the logtify module:
let { notifier } = require('logtify')();

// typeof notifier === 'object'

notifier.notify(new Error('Test error'));
notifier.notify('Hello world!');

However you can overcome it if you use plain ES5 require syntax:

const logtify = require('logtify')();
require('logtify-bugsnag')({ BUGS_TOKEN: 'YOUR_BUGSNAG_TOKEN' });
const notifier = logtify.notifier;

// typeof notifier === 'object'

notifier.notify(new Error('Test error'));
notifier.notify('Hello world!');

The subscriber will make sure that a message will be sent to Bugsnag if:

  • message.level === 'error'
  • process.env.BUGSNAG_LOGGING === 'true' || settings.BUGSNAG_LOGGING === true

To set the message.level to be error, make sure to use one of the following:

const { stream, logger } = require('logtify')();

stream.log('error', new Error('Hello world'), { my: 'metadata' }); // error can also be passed as an arg
logger.log('error', 'Hello world', { my: 'metadata' }); // or a string
logger.error('Hello world', { my: 'metadata'});

Or with a BugsnagAdapter:

const { notifier } = require('logtify')();

notifier.notify('Hello world');

An adapter also exposes standard bugsnag's requestHandler and errorHandler:

require('logtify-bugsnag')();
const { notifier } = require('logtify')();

notifier.requestHandler;
notifier.errorHandler;

Configuration

  • process.env.BUGSNAG_LOGGING = 'true' || BUGSNAG_LOGGING: true - Switching on / off the subscriber and adapter. On by default
  • process.env.BUGS_TOKEN = 'TOKEN' || BUGS_TOKEN: 'TOKEN' - your Bugsnag token
  • process.env.BUGSNAG_RELEASE_STAGES = 'production,staging' - comma separated list of bugsnag release stages

Settings: Module can be configured by both env variables or config object. However, env variables have a higher priority.

{
  BUGSNAG_LOGGING: true|false
  BUGS_TOKEN: 'YOUR_BUGSNAG_TOKEN'
  BUGSNAG_RELEASE_STAGES: ''
  BUGSNAG_APP_VERSION: '1.2.3'
  LOG_TIMESTAMP = 'true'
  LOG_ENVIRONMENT = 'true'
  LOG_LEVEL = 'true'
  LOG_REQID = 'true' // only included when provided with metadata
  LOG_CALLER_PREFIX = 'true' // additional prefix with info about caller module/project/function
}