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

@adr-center/pulse-support

v0.2.1

Published

ADR Pulse support reporting SDK and embeddable widget

Readme

ADR Pulse Support SDK

Install the public package and initialize it once in the host application:

npm install @adr-center/pulse-support
import { PulseSupport } from "@adr-center/pulse-support";

PulseSupport.init({
  apiUrl: "https://adr-pulse-52uewqsrka-ey.a.run.app",
  productKey: "ods-hub",
  environment: "production",
  appVersion: "2.6.0",
  getAuthToken: () => firebaseUser.getIdToken(),
}).installButton();

For a public or server-rendered application, its backend exchanges the private integration key for a short-lived reporter token at POST /api/v1/support/token. The integration key must never be included in browser code.

The same client can open the dialog from an existing application button:

const support = PulseSupport.init(config);
document.querySelector("#report-problem")?.addEventListener("click", () => {
  support.open({ type: "bug" });
});

React applications can import PulseSupportButton from @adr-center/pulse-support/react. The returned report reference and per-report status token are saved in local storage so the application can call client.getReport(reference) without exposing internal notes.

Show a person's requests

listReports() uses the current Firebase or short-lived reporter token and returns only requests created by that reporter for the configured product. Use status: "open" for a compact "My open requests" screen:

const openRequests = await support.listReports({ status: "open" });

When the support team asks for more information, the reporter can answer from the connected product. A request in waiting returns to investigating after the reply is accepted:

await support.reply(reportId, "The problem also happens in a private window.");

Notify when something changes

The watcher polls no more often than every 15 seconds and invokes the callback only after a known request changes. The host product remains in control of the notification UI:

const stopWatching = support.watchReports({
  intervalMs: 60_000,
  onChange: (report, previous) => {
    if (report.status === "resolved" && previous?.status !== "resolved") {
      showToast(`${report.title} has been resolved`);
    } else {
      showToast(`New support update: ${report.title}`);
    }
  },
});

// Call when the signed-in session or application is disposed.
stopWatching();

Reporter-visible updates are deliberately separate from internal investigation notes. The SDK never returns internal notes, diagnostics, ownership, or other people's requests.

The widget collects only the report text, optional files, and safe application context. Browser diagnostics are included only after the reporter selects the consent checkbox. Form values, credentials, tokens, and case content are never collected automatically.