Getting started

AtSail watches your app for production errors, groups them into issues, and opens pull requests that fix real bugs. To get started, install the SDK that matches your app and initialize it with your project's publishable key.

Install

bash
npm install @atsail/browser

Initialize

Call init() as early as possible in your app's entrypoint — before any other code runs, so AtSail can capture errors from the very first render.

js
import { init } from "@atsail/browser"; init({ publishableKey: "pk_live_...", });

Your publishable key is available on your project's Setup tab in the AtSail dashboard.

What gets captured

Once initialized, the SDK automatically captures:

  • Uncaught exceptions and unhandled promise rejections
  • Failed network requests (via fetch and XMLHttpRequest)
  • Overall request volume, used to compute an accurate error rate

No manual instrumentation is required for these. If you want to report something yourself, use captureException or captureMessage:

js
import { captureException } from "@atsail/browser"; try { riskyOperation(); } catch (err) { captureException(err); }

Environments

The SDK always captures and sends events — it doesn't ask which environment it's running in. Instead, your dashboard's project settings control which domains (production, staging, localhost, etc.) actually trigger AtSail's agent, so you can change that policy at any time without touching code.

Next steps

Once the SDK is installed and initialized, trigger a real error in your app (or wait for one to happen naturally) — it'll show up as an issue in your dashboard within a few seconds.