Set up
npm i pagerlessimport { init } from "pagerless/browser";
init({ key: import.meta.env.VITE_PAGERLESS_KEY, service: "dashboard" });What it catches
- Uncaught errors and unhandled promise rejections from
window, with the page path as the route. - Failing fetch calls (5xx, 429, network errors; not aborts or offline), from pagerless 0.2.0.
- Sent when the tab is hidden, so nothing is lost on close.
- Cross-origin "Script error." and browser-extension errors are ignored.
No heartbeats (a closed tab is not an outage) and no deploy markers. Ingest keys are write-only, so a key in your bundle cannot read anything; use a separate key for the browser so you can revoke it on its own.
Questions
Will a frontend error wake me at night?
Not by itself. Browser errors are rarely floor signals, so they are usually tell or log. Server-side floors are what wake you.