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

@askeladden/error-tracker-node

v4.1.2

Published

Error tracking for node, web and app environments.

Readme

error-tracker-node

Error tracking for node, web and app environments.

Prerequisites (for Sentry)

  • Add a project at https://sentry.io/askeladden-co/
  • Note down the DSN

You want to install the Sentry package that fits your project. Typically one of

Error tracking with AWS Lambda/serverles

This package does not support AWS Lambda yet. Follow docs for @sentry/serverless instead of using this package.

Install

yarn add @sentry/[react/react-native/node/browser]
yarn add @askeladden/error-tracker-node

Usage

// errorTracker.ts
import * as Sentry from '@sentry/[react/react-native/node/browser]';
import Tracker, { providers } from '@askeladden/error-tracker-node';

const environment = process.env.NODE_ENV || 'development';

const ErrorTracker = (() =>
  new Tracker(
    new providers.Sentry(Sentry, {
      dsn: process.env.SENTRY_DSN,
      environment,
      isActive: environment !== 'development',
    })
  ))();

export default ErrorTracker;

Remember to replace the Sentry import above, depending on what type of project you have.

// Somewhere in your own code
import errorTracker from './errorTracker';

try {
  // your-code
} catch (error) {
  errorTracker.error(error);

  // Extra context can also be added to simplify debugging
  errorTracker.error(error, {
    user: { id: 1234 },
    tags: ['auth'],
    myOwnKey: ['cake', 'pastry', 'banana'],
  });
}

If you do not have access to errorTracker where the error occurs, you can raise a ContextError. This context will be forwarded to Sentry.

import { ContextError } from '@askeladden/error-tracker-node';

throw new ContextError('Something bad happened', {
  user: { id: 1234 },
  tags: ['auth'],
  myOwnKey: ['cake', 'pastry', 'banana'],
});

Usage with React apps

If you're using React, you can hook into the built-in React ErrorBoundary by adding a wrapping ErrorBoundary component:

// ErrorBoundary.tsx
import React, { ReactNode, ErrorInfo } from 'react';
import ErrorTracker from './errorTracker';

type Props = {
  children: ReactNode;
};

class ErrorBoundary extends React.Component<Props> {
  componentDidCatch(error: Error, info: ErrorInfo) {
    const extraInfo = { stack: info.componentStack };
    ErrorTracker.error(error, extraInfo);
  }

  render() {
    const { children } = this.props;
    return children;
  }
}

export default ErrorBoundary;

// In App.tsx or similar location (where ThemeProvider lies)
export const RootElement = ({ children }) => (
  <ReduxProvider>
    <ErrorBoundary>
      <ThemeProvider theme={theme}>{children}</ThemeProvider>
    </ErrorBoundary>
  </ReduxProvider>
);