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

ngx-error-boundary

v0.0.3

Published

Angular 9 Component for React like Error boundary

Downloads

13

Readme

NgxErrorBoundary

This library is an experimental implementation of React Error boundary for Angular.

DEMO

Install the library

npm i ngx-error-boundary --save

Import the module:

imports: [NgxErrorBoundaryModule];

Once you include the module, you will get following component that you can use:

<ErrorBoundary
  [fallback]="template"
  key="unique.identify.string"
></ErrorBoundary>

following directives:

errorRetry;
errorDismiss;

and also you got one service:

NgxErrorBoundaryService;

Usage

<ErrorBoundary>

Using [fallback] with <ng-template></ng-template>, key is optional if there is only one ErrorBoundary pre-component.

If there are multi ErrorBoundary inside one component, you need to use key to show correct error message

<!-- error: {message: string, key: string} -->
<!-- retry$: Observable<boolean>: is retrying -->
<ng-template #errTemplate let-error let-retry$="retry$">
  <div class="err-container">
    <h2>Something goes wrong!</h2>
    <section>
      <p [innerHTML]="error.message"></p>
      <!-- errorRetry can help to retry the failed observable -->
      <button errorRetry>
        {{ (retry$ | async) ? "Retrying..." : "Retry" }}
      </button>
      <!-- errorDismiss: hide error boundary -->
      <button [errorDismiss]="error.key">Dismiss</button>
    </section>
  </div>
</ng-template>

<ErrorBoundary [fallback]="errTemplate" key="example">
  <YOUR_CONTENT_FROM_SERVER [data]="data$ | async" />
</ErrorBoundary>
this.data$ = timer(500).pipe(
  this.apiService.fetchData(),
  this.errorService.handleExpection({
    message: "Cannot load data",
    key: "example",
  })
);

When there is error, <YOUR_CONTENT_FROM_SERVER [data]="data$ | async" /> will be repalced with errTemplate.

@Input() fallback: TemplateRef

Take an ng-template as input.

@Input() key: string

A string to unqiue identify string to show correct error message


errorRetry Directive

You can retry the failed observable.

errorDismiss Directive

Take error's key string as input.

To hide Error boundary component


NgxErrorBoundaryService

handleExpection({message?: string, key?: string})

If nothing passed in as arguement, will use catched error's message information.

There is a default key assigned, can be used for global error message.

Example:

@Component({
  selector: "categories",
  ...
  providers: [NgxErrorBoundaryService],
})
export class CategoriesComponent {
  categories$: Observable<Category[]>;
  constructor(
    private categoriesService: CategoriesService,
    private errorService: NgxErrorBoundaryService
  ) {
    this.categories$ = this.categoriesService.fetchData().pipe(
      this.errorService.handleExpection({
        message: "Cannot load categories",
        key: "categories",
      })
    );
  }
}

dismiss(key?: string)

key: error key

Hide error boundary component and error message for the key.

If didn't pass key, then hide all error messages.