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

@joshmorony/signal-with-error

v0.0.5

Published

Convert an observable into two signals: one that contains the latest value, and another that contains any error

Downloads

9

Readme

toSignalWithError

Converts an observable into a pair of signals: value which will contain the success value or undefined, and error which will contain any error or undefined.

This provides a nice way to simply handle errors from observable streams using signals in a reactive/declarative way.

You can also optionally pass an initial value like this:

toSignalWithError(obs$, 5);

If an initial value is not supplied, it will be assumed that the observable you supply is synchronous (if it is not, the signal will throw an error).

Example Usage

  data = toSignalWithError(this.getFromAPI())

  getFromAPI() {
    return of(null).pipe(
      delay(2000),
      switchMap(() =>
        this.http.get<any>("https://jsonplaceholder.typicode.com/todos")
      )
    );
  }
<p>Let's load some data!</p>
<ul>
  <ng-container *ngIf="myService.data.value(); else loading">
    <li *ngFor="let todo of myService.data.value()">{{ todo.title }}</li>
  </ng-container>
  <ng-template #loading>
    <li *ngIf="!myService.data.error(); else failed">They see me loadin'...</li>
  </ng-template>
  <ng-template #failed>
    <p>Uh oh... you're on your own buddy:</p>
    <small> {{ myService.data.error().message }} </small>
  </ng-template>
</ul>