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

@toruslabs/loglevel-sentry

v7.0.1

Published

A package to allow logging and monitoring with sentry

Downloads

5,079

Readme

loglevel-sentry

npm version npm

Introduction

This repo allows you to log + track logs using sentry

Features

  • Typescript compatible. Includes Type definitions

Installation

Bundling

This module is distributed in 3 formats

  • esm build dist/loglevelSentry.esm.js in es6 format
  • commonjs build dist/loglevelSentry.cjs.js in es5 format
  • umd build dist/loglevelSentry.umd.min.js in es5 format without polyfilling corejs minified

By default, the appropriate format is used for your specified usecase You can use a different format (if you know what you're doing) by referencing the correct file

The cjs build is not polyfilled with core-js. It is upto the user to polyfill based on the browserlist they target

Directly in Browser

CDN's serve the non-core-js polyfilled version by default. You can use a different

jsdeliver

<script src="https://cdn.jsdelivr.net/npm/@toruslabs/loglevel-sentry"></script>

unpkg

<script src="https://unpkg.com/@toruslabs/loglevel-sentry"></script>

Usage

Add @toruslabs/loglevel-sentry to your project:

To use this module:

  1. Install the package npm i @toruslabs/loglevel-sentry

  2. Create your loglevel instance and install this plugin to enable Sentry:

import loglevel from "loglevel";
import * as Sentry from "@sentry/browser";
// Node.js: import * as Sentry from "@sentry/node";
import LoglevelSentryPlugin from "@toruslabs/loglevel-sentry";

logger = loglevel.getLogger("__LOGGER_NAME__");

const plugin = new LoglevelSentryPlugin(Sentry);
sentry.install(logger);

(Optional) You can replace loglevel with other logging library by using loglevel methodFactory API:

import loglevel from "loglevel";
import pino from "pino";
import * as Sentry from "@sentry/browser";
// Node.js: import * as Sentry from "@sentry/node";
import LoglevelSentryPlugin from "@toruslabs/loglevel-sentry";

const logger = loglevel.getLogger("__LOGGER_NAME__");
logger.methodFactory = (method, level, name) => {
  const alt = pino(name, level);
  return alt[method];
};

const sentry = new LoglevelSentryPlugin(Sentry);
sentry.install(logger);

Info

Is 100% compatible with loglevel API. Events/errors will be reported for all enabled log functions.

Best practices

Though it isn't compulsory, it is recommended to call log functions with following signatures:

  • log.trace, log.debug, log.info, and log.warn: (msg: string, ...others: any[]).

  • log.error: (err: Error, ...others: any[]).

If you always want to monitor a specific event regardless of configured log level, use the plugin API:

const sentry = new LoglevelSentryPlugin(Sentry);
sentry.install(logger);

sentry.trace("this", "message", "will always be reported.");

Requirements

  • This package requires a peer dependency of @babel/runtime
  • Node 18+