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

@errordock/core

v0.1.0-rc.1

Published

The platform-neutral half of the ErrorDock JavaScript SDKs: queue, transport, sessions and remote configuration.

Readme

@errordock/core

The platform-neutral half of the ErrorDock JavaScript SDKs. You almost certainly want @errordock/browser or @errordock/react-native instead — this package is what both of them are built on, and it is installed alongside either one.

npm install @errordock/core

What is in here

The parts of an SDK that have nothing to do with where it is running:

  • the event model — the wire shape the ingest endpoint accepts, with no translation layer
  • two bounded queues, drop-oldest and batched — events and spans, separately, because spans outnumber events by roughly two orders of magnitude and a shared queue would let a busy minute of tracing evict the errors
  • the transport — retry with backoff, Retry-After on 429, requeue on 5xx and on a network failure, drop on a 4xx the server has already judged, and a separate backoff per queue so a tracing quota refusal leaves errors flowing
  • tracing — spans, W3C trace ids, head sampling decided at the root
  • sessions and the install id, with the rotation rules the whole product depends on
  • remote configuration, with last known good cached and a fail-open default
  • the never-throw guarantee: every entry point swallows its own failures

What is not

Anything that needs a platform. window.onerror, the History API, localStorage, AppState, ErrorUtils, and every other hook lives in the package for that platform. This one compiles without the DOM library, so a stray document is a build error rather than a crash on somebody's phone.

Writing a host

A host subclasses ErrorDockCore and lends it what it cannot know:

import { ErrorDockCore, type CoreHost } from "@errordock/core";

const host: CoreHost = {
  persistent: myKeyValueStore,   // survives a restart: the install id, the config cache
  sessions: myKeyValueStore,     // scoped to this run
  keepalive: false,              // only a browser has it
  describeDevice: () => ({ platform: "ios" }),
};

Everything else — the queue, the transport, the filters — is already written, already tested, and shared with every other host.

Licence

MIT. The ErrorDock service itself is proprietary; this SDK is not.