Racna

Interactive playground

A clicking playground for every kind of error Racna can capture. Each button below fires one specific scenario; watch the Racna badge, panel, or toast react, and the log on the right confirms what fired. You need the Racna extension installed, with this site switched on from the toolbar popup (on localhost it is enabled out of the box).

Running from a clone rather than the live site? Serve this folder over a static server: run serve.cmd in this folder (or npx http-server docs/harness -p 8000 -o from the project root), then open http://localhost:8000.

Console kind: console

Uncaught kind: uncaught

The synthetic ErrorEvent has filename + lineno but no error object, so the Racna modal renders Location instead of Stack Trace.

Promise rejection kind: rejection

Network (fetch) kind: network

Slow + abort exercises the duration field on the network entry, so you should see a ~3000 ms reading on the resulting Network Error.

Network (XHR) kind: network

Copy format payloads kind: network

For the copy/export checks. With Hide sensitive headers on, the first entry copies with Authorization: [redacted]. In the AI format, the second entry's request body carries a [body truncated at 50000 characters] marker and the third is wrapped in a lengthened four-backtick fence. (Page JavaScript cannot send a Cookie header, so Authorization and X-Api-Key stand in for the credential set.)

Breadcrumb scenarios

After triggering, open the resulting entry's modal; the Breadcrumbs section should show the preceding activity in order, each tagged with its type (LOG / HTTP / NAV / CLICK).

Watch / Ignore matching

Use these to test your Watch / Ignore rules. Create a rule first in Racna (eye icon for Watch, eye-off for Ignore), then fire the matching error and verify the toast appears (Watch) or the entry is suppressed (Ignore).

Burst

Flood / lag throttle · dedup · circuit breaker

The A,B,A,B loop should settle into exactly two rows with climbing ×counts (not 80 rows) and stay smooth. The route loop should produce one row per path (no false merge). The flood should pause capture and show the ⚠ banner; already-captured entries stay clickable, and Resume re-opens capture (re-pausing if the flood is still running).