Find and report problems in programs run with Elide.
Read errors
elide --error-format=plain run app.js
Plain errors go to stderr with a short stack; program output stays on stdout. --verbose or --debug adds Elide’s
own logs.
~/demo elide ./checkout.js
╭Script Error────────────────────────────────────────────────────────────────╮
│ RangeError: discount must be a fraction, got 25 │
│ │
│ In file checkout.js:3:11: │
│ ╭─ │
│ 2 │ if (pct > 1) { │
│ → 3 │ throw new RangeError(`discount must be a fraction, got ${pct}`); │
│ 4 │ } │
│ 5 │ return order.total * (1 - pct); │
│ 6 │ } │
│ · │ │
│ Stack Trace──────────────────────────────── │
│ ╭─ [js] applyDiscount checkout.js:3:11-67 │
│ │ │
│ · elide ./checkout.js │
│ Advice──────────────────────────────────────────────────────────────────── │
│ An error occurred while executing your code. │
╰────────────────────────────────────────────────────────────────────────────╯
| Flag | Effect |
|---|---|
--abort-on-uncaught-exception |
Print the error, then raise SIGABRT (exit 134) so the OS writes a core dump. |
--redirect-warnings= |
Write process warnings, such as process.emitWarning(), to FILE, not stderr. |
--timeout=DURATION |
Stop the program after DURATION (for example 30s) with exit 124. |
--max-mem=SIZE |
Limit the heap size, for example 512m. Exceeding it fails with a nonzero exit. |
~/demo elide --profiler=cputracing pricing.js
total: 48
╭Profiler Report───────────────────────────────────────────────────────────────────────────────────╮
│ Location Root Total Interpreted Compiled │
│ pricing.js price 1 50.0% 1 100.0% 0 0.0% │
│ pricing.js :program 1 50.0% 1 100.0% 0 0.0% │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
~/demo elide --debugger=dap pricing.js
[Graal DAP] Starting server and listening on /127.0.0.1:4711
Attach a debugger
| Program | Flag | Listens on | Client |
|---|---|---|---|
| JavaScript, TypeScript, Python | --debugger=cdp |
ws://127.0.0.1:1337/… |
Chrome DevTools or any CDP client |
| JavaScript, TypeScript, Python | --debugger=dap |
127.0.0.1:4711, waits for a client |
Any DAP-capable editor |
| Java, Kotlin | --debugger |
127.0.0.1:5005 (JDWP), suspended |
IntelliJ IDEA, VS Code, jdb |
elide run --debugger=cdp app.js
Debugger listening on ws://127.0.0.1:1337/<id>/inspect
For help, see: https://elide.help/docs/debugging
E.g. in Chrome open: devtools://devtools/bundled/js_app.html?ws=127.0.0.1:1337/<id>/inspect
Open the devtools:// link in Chrome.
elide run --debugger=dap app.js
elide run --debugger Hello.kt
Listening for transport dt_socket at address: 5005
Change a listener’s address with --debugger-host and --debugger-port:
elide run --debugger=dap --debugger-port=5678 app.js
elide run --debugger=0.0.0.0:5005 Hello.kt
DAP also accepts --debugger-port=0 to let the OS assign an available port. The listening message contains the
actual port; execution waits until the client finishes configuring breakpoints.
Controllers can set ELIDE_DEBUGGER_METADATA=1 when launching with a loopback address. After binding, stderr emits
an ASCII record separator (0x1e), followed by ELIDE_DEBUGGER and a JSON record:
{"version":1,"event":"listening","mode":"dap","host":"127.0.0.1","port":49152}
Read the assigned port from this record rather than reserving and releasing a port before launch. The record is opt-in and is emitted only for a verified loopback listener. CDP requires a fixed port.
A number or host:port after --debugger is a JDWP address and applies to Java and Kotlin only. JDWP has no
authentication: bind beyond loopback only on a trusted network, or use an SSH tunnel.
The DAP port has no secret: any process on the host can attach, so use --debugger=dap only on a single-user host.
In an Android project, elide run --debugger launches the app suspended on a device and forwards its JDWP port
to loopback (Run and debug).
Debug tests
elide test --debugger
elide test --debugger=dap sample.test.mts
elide test --debugger=5005
| Flag | Debugs |
|---|---|
--debugger |
JavaScript tests over CDP and JVM tests over JDWP on 5005 |
--debugger=cdp or dap |
JavaScript tests only |
--debugger=PORT |
JVM tests only |
A path narrows JavaScript tests to one file; narrow JVM tests by package name. While a debugger is attached, JavaScript test files run one at a time.
Debug in Tern
The Tern plugin debugs a project’s JavaScript, TypeScript and Python sources and JavaScript and TypeScript
tests: launch from the project workspace, set file:line or gutter breakpoints, step with F10, F11 and Shift+F11, and
inspect frames and values. See Debugging in Tern.
Measure coverage
elide run --coverage app.js
Elide prints a Coverage Report after the program exits, with statements, lines and functions covered per file.
JavaScript and TypeScript coverage is also written as LCOV to .dev/reports/coverage/js/run/lcov.info in the project,
or in the working directory outside one.
Profile CPU time
elide run --profiler=cputracing app.js
╭Profiler Report───────────────────────────────────────────────────────────────╮
│ Location Root Total Interpreted Compiled │
│ app.js fib 21.89k 100.0% 21.89k 100.0% 0 0.0% │
│ app.js :program 1 0.0% 1 100.0% 0 0.0% │
╰──────────────────────────────────────────────────────────────────────────────╯
Total counts calls to each function. For JFR recordings, heap dumps and Linux perf, see
Monitoring and Profiling.
Trace with Insights
// insight.js
insight.on("enter", (ctx) => {
console.log("enter", ctx.name);
}, { roots: true });
elide run --insights=insight.js app.js
Each function entry prints a line such as enter fib. See the Insights API for events and filters.
Report a bug
elide info
elide agent diagnostics
elide agent bug
elide agent bug prints the issue tracker URL and a Markdown report template. Fill in the exact command, the expected
behavior, and any crash report.