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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@sentry/deno

v10.65.0

Published

Official Sentry SDK for Deno

Readme

Official Sentry SDK for Deno (Beta)

npm version npm dm npm dt

Links

The Sentry Deno SDK is in beta. Please help us improve the SDK by reporting any issues or giving us feedback.

Usage

To use this SDK, call Sentry.init(options) as early as possible in the main entry module. This will initialize the SDK and hook into the environment. Note that you can turn off almost all side effects using the respective options.

import * as Sentry from 'npm:@sentry/deno';

Sentry.init({
  dsn: '__DSN__',
  // ...
});

To set context information or send manual events, use the exported functions of the Deno SDK. Note that these functions will not perform any action before you have called init():

// Set user information, as well as tags and further extras
Sentry.setExtra('battery', 0.7);
Sentry.setTag('user_mode', 'admin');
Sentry.setUser({ id: '4711' });

// Add a breadcrumb for future events
Sentry.addBreadcrumb({
  message: 'My Breadcrumb',
  // ...
});

// Capture exceptions, messages or manual events
Sentry.captureMessage('Hello, world!');
Sentry.captureException(new Error('Good bye'));
Sentry.captureEvent({
  message: 'Manual',
  stacktrace: [
    // ...
  ],
});

Auto-instrumentation (experimental)

Some libraries (e.g. mysql) don't emit tracing signals on their own. To instrument them, Sentry uses orchestrion to transform them at load time so they publish to node:diagnostics_channel.

In Deno versions prior to 2.8.0, this is not available, as it relies on Module.registerHooks, which was added in that version.

As of Deno 2.8.3, you can use the --import or --preload argument to deno run in order to enable these instrumentations.

$ deno run --import=@sentry/deno/import app.ts

[!NOTE] In Deno versions 2.8.0 through 2.8.2, a bug causes Deno to deadlock when a module hook is added in this way. As a workaround, you can import the loader explicitly, and then dynamically import your app to take advantage of the added module loading hooks.

import 'npm:@sentry/deno/import';
await import('./app.ts');

In both cases, your app.ts should simply load Sentry as usual:

// app.ts

// initialize Sentry as early as possible
import * as Sentry from 'npm:@sentry/deno';
Sentry.init({ dsn: '__DSN__' });

// ... the rest of the app...