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

@ebdev/angular-monitor

v0.1.1

Published

In-app runtime for the Angular Performance Monitor DevTools extension — the collectors for change-detection attribution, signal graphs, and RxJS call sites, which have to run inside your Angular app.

Downloads

137

Readme

@ebdev/angular-monitor

The in-app runtime for the Angular Monitor Chrome DevTools extension.

This package only collects data inside your app. The viewer is the DevTools panel — install it from the Chrome Web Store before you wire this in. Docs, a live demo, and the full product live at angular-monitor.ebdev-design.com.

Angular exposes no public API that lets an extension read change detection, signals or RxJS from outside the app, so the collectors run inside it. This package is where they live: the DevTools panel is the viewer, and it has nothing to show until your app provides it.

Install

npm install @ebdev/angular-monitor
# pnpm add @ebdev/angular-monitor
# yarn add @ebdev/angular-monitor

Usage

import { bootstrapApplication } from '@angular/platform-browser';
import { providePerformanceMonitor } from '@ebdev/angular-monitor';
import { AppComponent } from './app/app.component';

bootstrapApplication(AppComponent, {
  providers: [providePerformanceMonitor()],
});

It is a no-op while the DevTools panel isn't open, and you'll usually want it in your development build only.

Development-only wiring

import { isDevMode } from '@angular/core';

bootstrapApplication(AppComponent, {
  providers: [...(isDevMode() ? [providePerformanceMonitor()] : [])],
});

API

| Export | Description | | --- | --- | | providePerformanceMonitor(options?) | EnvironmentProviders that installs the bridge during app bootstrap. | | installRuntimeBridge() | Installs the bridge manually, outside Angular's DI. Returns a RuntimeHandle. | | RuntimeController | The controller class backing the bridge. | | detectCapabilities() | Reports the detected AngularEnvironment (version, zone/zoneless, signals, RxJS). | | safeCollect(fn, onError?) | Runs a collector, swallowing and reporting errors instead of breaking your app. | | notifySignalWrite() / notifyComputed() / notifyEffect() | Manual instrumentation hooks for signal activity. |

Options

providePerformanceMonitor({ level }) accepts a MonitorLevel of 0 | 1 | 2 | 3, trading detail for overhead — 0 collects the least, 3 the most.

Requirements

  • rxjs ^7.8.0 — a peer dependency. It must resolve to the same rxjs instance your app uses; the RxJS collector patches Observable.prototype.subscribe and cannot see subscriptions created by a second, duplicate copy of rxjs.
  • @angular/core >=17 <23 — an optional peer dependency. Required for providePerformanceMonitor(); the standalone helpers work without it.

Privacy

The runtime sends data only to the DevTools panel on the same page, over postMessage. Nothing is transmitted off-device. See the privacy policy.

License

MIT © Eliran Bar