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

@givve/errors

v4.4.4

Published

This package adds Sentry error handling to your project.

Downloads

19

Readme

Npm package @givve/errors

This package adds Sentry error handling to your project.

Settings

Sentry dsn property needs to be set. To be able up use SourceMaps, for every app deployment a sentry release needs to be created and artifacts uploaded. To use those Sentry.init needs the release version added to the congif. Optionally a 'release' can be set.

Sentry accepts a version as 'release' property in the init options. This version value needs to be prefixed with the sentry project name. E.g. [email protected]

The package.json version can be set in the environment.ts file.

export const environment = {
  production: false,
  sentry: {
    dsn: '',
    // this is the sentry project name
    releasePrefix: 'my-project',
  },
  version: require('../../package.json').version
};

In app.module.ts

import { ErrorsModule, ErrorsNoopModule } from '@givve/errors';
import * as Sentry from '@sentry/browser';


const dsn = (env as any).sentry && (env as any).sentry.dsn ? (env as any).sentry.dsn : null;
const release = (env as any).sentry && (env as any).sentry.releasePrefix ? `${(env as any).sentry.releasePrefix}@${env.version}` : null;

if (dsn) {
  const options = {dsn};
  if (release) {
    Object.assign(options, {release});
  }
  Sentry.init(options);
}

// optionally ignore unauthenticated 401 request errors
const config = {ignoreStatus: [401]};
const errorsModule = dsn ? ErrorsModule.forRoot(config) : ErrorsNoopModule;

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,
    errorsModule
  ],
  bootstrap: [AppComponent]
})
export class AppModule { }

Set 'sentry.dsn' property in the environment.ts if you want to use Sentry error monitoring, e.g. environment.prod.ts

Because the notificationService.captureException can be called from anywhere, e.g. from the http interceptor catching a 401, the ErrorsNoopModule has to be imported in case 'sentry.dsn' is not set.

To submit a user alongside your errors, call notificationService.setUser after the login with the user object containing the following data:

export interface SentryUserData {
  id: string;
  username: string;
}