HTTP decode-stack
The OpenAPI 3.1 document is generated beside this preview as openapi.json. Schemas document current behavior; they never validate runtime requests. The built-in server is loopback/host-guarded and has no authentication.
decodeStack
Decode a stack trace
decodeStack description
Decodes a Hermes bytecode (index.hbc) or JS bundle (index.js) stack trace to original TypeScript source locations. Only lines containing .hbc or .js frames are processed. Without a SHA or build directory, the server resolves frames against the most recent local build under its own root. Input with no recognisable frame lines returns 400 with code NO_FRAMES_DECODED. When frames are found but cannot be resolved, for example because no matching source maps exist, the response is still 200 and each such frame carries a non-null error.
decodeStack contract
POST /api/decode-stack
Responses: 200, 400, 500; middleware can also return 403, 408 or 429.
decodeStack see also
decodeStack body.stackTrace
Raw stack trace text; surrounding log noise is ignored and only .hbc or .js frames are extracted.
decodeStack body.sha
Source map SHA, at least 8 hex characters; auto-detected from the input when omitted.
decodeStack body.buildDir
Build directory containing source maps; auto-detects dist-dev or dist-build when omitted.
decodeStack body.context
Lines of source context around each frame, from 0 to 50; defaults to 2.
decodeStack body.dclDirs
Maps each DCL library name to its build directory for multi-bundle decoding.
Updated about 3 hours ago