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

ng-error-reporter

v1.0.10

Published

Angular http error reporter

Downloads

13

Readme

NG-Error-Reporter

A simple library to report errors from http requests to a server.

Minimum requirements

Angular 15.0.0

Installation

npm install ng-error-reporter

Usage

Import the RouterModule in your module and call the forRoot method with the configuration object.

import {provideReporterInterceptor} from "./reporter.module";

@NgModule({
  imports: [
    // import the module with the correct configuration
    ReporterModule.forRoot({
      whitelist: {
        urls: [],
        codes: [500, 418]
      },
      blacklist:
        {
          urls: [],
          codes: []
        }
    })
  ],
  providers: [
    // Will add the reporter interceptor to the http requests
    provideReporterInterceptor()
  ],
})

After the module is imported and the interceptor is provided, the errors will be catched and sent to the application by the reporter service.

import {ReporterService} from "./reporter.service";
import {ErrorResponse} from "./reporter-errors.types";

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.css']
})
export class AppComponent {
  constructor(private reporter: ReporterService) {
    this.reporter.errors.subscribe((errors: ErrorResponse[]) => {
      // You can get the latest error from the reporter service if needed
      console.log(this.reporter.getLatestError()
    });
  }
}

Configuration

The configuration object has two properties, whitelist and blacklist. Both properties have two properties, urls and codes. The urls property is an array of strings that will be used to match the url of the request. The codes property is an array of numbers that will be used to match the status code of the response.

The whitelist property will only report the errors that match the urls and codes. The blacklist property will report all errors except the ones that match the urls and codes.

Types

ErrorResponse

export type ErrorResponse = {
  triggeredAt: Date;
  code: number;
  message: string;
  others: any;
  request: ReporterErrorRequest;
}

export type ReporterErrorRequest = {
  url: string;
  method: string;
  payload: any;
  params: any;
}

License

MIT