Spool

What it does

• Catch errors from JavaScript, Python and Go apps
• Group repeats into a single issue
• Trace browser errors back to the original source lines using your source maps
• Download an evidence packet to hand to someone fixing the issue
• Give an agent read-only access to a single project
• Show when a fixed error comes back in a later release
• Mark issues acknowledged, resolved or suppressed
• Export private evidence and restore it into a fresh copy

What it promises

• ERR-003Error details are scrubbed before they are stored: no headers, cookies, request bodies or user identity are kept.
• ERR-004Owner sign-in, error sending and read-only agent access are separate, and revoking one takes effect immediately.
• ERR-002An error is only counted once it is fully saved, and a repeated send never counts twice.
• ERR-006A resolved issue is flagged as returning only when it appears in a later release; an old release's error does not trigger a false alarm.
• ERR-005Source maps are matched by project, release and build; if a map is missing or wrong, the original frame is kept rather than guessed.
• ERR-004Your private source maps are never public.
• ERR-008Counts of errors accepted and rejected are visible, and Spool does not claim complete coverage.
• ERR-009Archives restore into an empty installation only after being checked, so a bad archive leaves nothing half-restored.
• ERR-010A new installation starts with no demo data.

Move in from

• Sentry (point your existing error reporting at Spool)

Run it yourself

Install the command once, then clone a product and start it.

$ npx -y @runeditrun/rer cli install
$ git clone https://github.com/just-every/run-spool
$ cd run-spool && rer dev

No npm? curl -fsSL https://runeditrun.com/install.sh | sh installs the same command.