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

@mobile-surfaces/traps

v9.0.0

Published

Single home for the trap catalog, MobileSurfacesError base, URL builder, and generated TS/Swift bindings. Imported by every package that throws or reports diagnostics; not user-facing.

Readme

@mobile-surfaces/traps

Catalog, error base, URL builder, and Swift binding codegen for Mobile Surfaces. Imported by every other Mobile Surfaces package that throws or reports diagnostics; not user-facing.

What lives here

  • MobileSurfacesError: abstract base class. Every error thrown by @mobile-surfaces/push, @mobile-surfaces/surface-contracts, @mobile-surfaces/live-activity, and @mobile-surfaces/validators ultimately derives from this. Lazy trapId and docsUrl getters resolve through the generated bindings, so subclasses only set this.name.
  • TRAP_BINDINGS and TrapIds: generated from data/traps.json at the repo root. Includes the runtime-reachable subset of every trap entry (id, title, severity, detection, summary, symptom, fix, docsUrl, plus optional deprecated and siblings cross-refs).
  • docsUrlFor(id, title): single URL builder. Every renderer (the generator, scripts/build-agents-md.mjs, the CLI error formatter) imports from here, so the slug algorithm cannot drift.
  • swift/MobileSurfacesTraps.swift: generated Swift MSTrapBound protocol + MSTraps lookup table. Byte-identity replicated into packages/live-activity/ios/ (for the native module pod) and apps/mobile/targets/_shared/ (for widget + notification-content extensions via the _shared/ auto-membership convention). MS040 enforces the three copies stay in sync.

Release group

@mobile-surfaces/traps ships in the linked release group with @mobile-surfaces/surface-contracts and @mobile-surfaces/validators. The three packages always bump majors together; the rest of the monorepo versions independently. See notes/refactor-v7.md.

Regenerating

Edit data/traps.json. Then run:

node --experimental-strip-types scripts/generate-traps-package.mjs

pnpm surface:check runs the generator with --check to fail CI on drift.