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

@sparshlabs/angular

v0.1.0

Published

Angular binding for sparsh: [sparshGuard], [sparshGuardTarget], provideActivationGuard().

Readme

@sparshlabs/angular

Angular directives and an app-wide provider for Sparsh.

npm install @sparshlabs/angular

Guard a region of your app by putting sparshGuard on any element. The element itself becomes the guard root, so no wrapper element is added:

import { Component } from '@angular/core'
import { ActivationGuardDirective, type Decision } from '@sparshlabs/angular'

@Component({
  selector: 'app-root',
  imports: [ActivationGuardDirective],
  template: `
    <main sparshGuard mode="report" (suspect)="onSuspect($event)">
      <app-inbox />
    </main>
  `,
})
export class AppComponent {
  onSuspect(decision: Decision) {
    console.info('Suspicious activation', decision)
  }
}

Or guard the whole document from app.config.ts:

import { provideActivationGuard } from '@sparshlabs/angular'

export const appConfig = {
  providers: [provideActivationGuard({ mode: 'report' })],
}

mode defaults to enforce; start with report to observe decisions before enabling blocking. The directive's inputs can change at runtime (the guard is recreated only when an option that matters changes). provideActivationGuard() options are fixed for the injector's lifetime.

[sparshGuardTarget] exposes an isGuarded() signal for one element, resolved against the nearest [sparshGuard] or the app-wide guard:

<button sparshGuardTarget #g="sparshGuardTarget" [class.blocked]="g.isGuarded()">Delete</button>

A nested sparshGuard creates an independently configured guard for its subtree. Guards start after the first render and never run during server-side rendering. Angular 22 or newer is required.

See the repository README and API source.