Documentation

Guides for protecting production JavaScript

Reference guides for release workflows, command-line usage, cross-file protections, and the desktop app.

Build and Release Workflows Download Desktop App
Inside the Docs

Practical guides for real release work.

How-to guides Start with release sequencing and command-line usage, then move into feature-specific references.
Advanced protection Browse cross-file controls like Replace Globals and Protect Members when a build spans multiple scripts.

Explain-error preview

Paste a protected-output runtime error into the box below. The browser-side rule engine diagnoses the most likely JSO transform that caused it and recommends a concrete fix — identifier to exclude, option to toggle, file pattern to skip. No API key. No data leaves your browser. Same matchers the server-side /v1/ai/explain-error.ashx endpoint runs in preview mode.

1. Paste the error

2. Diagnosis

No error supplied yet.
Rule-based local preview — same matchers as /v1/ai/explain-error.ashx when no provider key is configured. Provider-backed API calls can reason about novel errors the rules don't recognize; the rules stay on as the circuit-breaker fallback. Common patterns produce identical answers either way.

How this composes

This preview is most useful paired with a production beacon. Wire your CDN to forward unhandled-error events at error from protected pages to a small webhook; the webhook calls explain-error server-side and posts the diagnosis into your incident channel. The full production-triage composition is documented at AIErrorRouting.aspx.

If your error doesn't match any rule, paste it into a support ticket — new rules get added based on what real customers hit. The bar is high-signal, not coverage: a rule that fires on one well-defined pattern beats a fuzzy rule that fires on three.

Try this in the online obfuscator

Paste your own code and see this option applied, or compare plans for larger projects and the desktop app.

Try It Free See Pricing