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

@debugr/sentry

v3.0.0-rc.2

Published

Sentry log handler for Debugr

Downloads

8

Readme

Sentry Log Handler for Debugr

This LogHandler will forward errors to Sentry.

This plugin does not use the Sentry SDK, because it's incompatible with AsyncLocalStorage, which Debugr makes heavy use of.

Installation

npm install --save @debugr/sentry

Usage

import { Logger, LogLevel } from '@debugr/core';
import { SentryHandler } from '@debugr/sentry';

const globalContext = {
  applicationName: 'example',
};

const logger = new Logger(globalContext, [
  new SentryHandler({
    dsn: 'https://[email protected]/123',
  }),
]);

logger.setContextProperty('jobName', 'sentryTest');

logger.error(new Error('App crashed!'));

Options

The SentryHandler constructor accepts an optional options object as the first argument. The available options are:

| Option | Type | Default | Description | |-----------------------|-------------------------------|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | dsn | string | (none) | The Sentry DSN. If unspecified or empty, the handler will not do anything. | | breadcrumbThreshold | LogLevel | LogLevel.DEBUG | The minimum level for entries to be collected as breadcrumbs. | | captureThreshold | LogLevel | LogLevel.ERROR | The minimum level at which entries should be captured and sent to Sentry. A captured entry will send all breadcrumbs collected within the same task prior to the entry being captured. | | captureProbability | number | 1 | The probability, as a float in the range <0, 1>, with which captured entries will be actually sent to Sentry. For example a value of 0.1 means 10% probability, so roughly 1 in every 10 captured entries will be sent. | | captureWholeTasks | boolean | true | Whether to wait for a task to finish before sending captured entries to Sentry. If this is set to true (the default), only the last entry captured within a task will be sent, with all prior captured entries from the same task included in the breadcrumbs. When set to false, each entry captured within a task will be sent immediately, including all prior breadcrumbs, which could result in multiple separate entries in Sentry when an error is logged multiple times. | | extractMessage | (entry: LogEntry) => string | (see description) | A callback which should extract a string message from a LogEntry. By default, if an error is part of the entry, its message is used; otherwise the entry message is used, if present; and finally a generic string is generated. | | levelMap | Record<number, string> | (none) | A map of custom log levels to Sentry log levels. Sentry recognises the following log levels: debug, info, warning, error and fatal. |