Parse stack traces into root frames, files, and app code
Paste a production stack trace to detect the runtime, separate app frames from dependencies, and find the first frame worth investigating.
Runs locally in your browser. Pasted stack traces are analyzed in memory and are not sent to Squasher.
Paste a stack trace
JavaScript trace with 4 parsed frames. Start at /app/src/cart/summary.ts:42.
Detected JavaScript.
4 frames detected.
calculateCartTotal in /app/src/cart/summary.ts
/app/src/cart/summary.ts:42:17
/app/src/components/checkout-summary.tsx:18:11
/app/node_modules/react-dom/cjs/react-dom-client.development.js:5529:22
/app/node_modules/react-dom/cjs/react-dom-client.development.js:17641:20
Useful enough for the immediate debugging job.
Each utility is product-adjacent by design: it solves a concrete setup or debugging problem, then links to the Squasher workflow that monitors it continuously.
Detects JavaScript, Python, JVM, Ruby, and Go-shaped traces.
Highlights dependency frames such as node_modules, site-packages, gems, and runtime internals.
Selects the first app frame as the likely investigation starting point.
Monitor stack traces with release, replay, logs, and AI triage attached.
Use the parser for one-off debugging, then send production errors to Squasher when the same workflow should happen automatically.