node-js 0.1.15

JavaScript as a fusevm frontend: a lexer/parser and compiler to fusevm::Chunk on a JsHost object heap, with no bespoke VM or JIT
Documentation
.TH NODE 1 "2026-11-10" "node-js 0.1.15" "User Commands"
.SH NAME
node \- JavaScript on fusevm, a compiled JS runtime (bytecode VM + Cranelift JIT)
.SH SYNOPSIS
.B node
[\fIOPTIONS\fR] [\fIFILE\fR] [\fIARGS\fR...]
.br
.B node
\fB\-e\fR \fISRC\fR [\fIARGS\fR...]
.SH DESCRIPTION
.B node-js
lexes and parses JavaScript and lowers it to
.B fusevm
bytecode executed on a Cranelift JIT over a JsHost object heap.
There is no bespoke VM or JIT; execution and codegen live in fusevm.
Object, string, and array cells ride through the VM as handles into that heap.
.PP
With no
.B \-e
and no
.I FILE
argument,
.B node
starts the REPL when standard input is a terminal, and otherwise reads a
script from standard input and runs it.
.SH OPTIONS
.TP
.B \-e \fISRC\fR, \-\-eval \fISRC\fR
Evaluate a one\-liner instead of a file.
.TP
.B \-p \fISRC\fR, \-\-print \fISRC\fR
Evaluate a one\-liner and print its completion value, as
.B node \-p
does. With both
.B \-e
and
.B \-p
present, the last one on the command line wins.
.TP
.B \-\-repl
Start the interactive REPL. This is also the default with no
.I FILE
argument on a terminal.
.TP
.B \-\-lsp
Speak the Language Server Protocol over stdio. Takes no
.IR FILE .
.TP
.B \-\-dap
Speak the Debug Adapter Protocol over stdio. Takes no
.IR FILE .
.TP
.B \-\-build
Ahead\-of\-time compile
.I FILE
to a standalone native executable instead of running it. The executable is
written next to the source, named by the source file stem (\fIfoo.js\fR
becomes \fIfoo\fR), and the bytecode cache is warmed.
.TP
.B \-\-dump\-bytecode
Print the compiled fusevm bytecode for
.I FILE
and exit, instead of running it. Distinct from
.BR \-\-disasm ,
which prints a formatted disassembly listing.
.TP
.B \-\-no\-warnings
Silence all
.B process.emitWarning
output.
.TP
.B \-\-no\-deprecation
Silence DeprecationWarnings only.
.TP
.B \-\-trace\-warnings
Suppress the one\-time
.RB "(Use `" "node \-\-trace\-warnings ..." "`)"
hint. Unlike Node, this does not add a creation stack to the warning.
.TP
.B \-\-trace\-deprecation
The same, for DeprecationWarnings.
.TP
.B \-\-dump\-tokens
Print the lexer token stream for
.I FILE
(one \fIline\fR and token per line) and exit, instead of running it.
.TP
.B \-\-dump\-ast
Print the parsed AST for
.I FILE
and exit, instead of running it.
.TP
.B \-\-tiers
Run it, then report which fusevm execution tier took each of its chunks.
.TP
.B \-\-disasm
Print a fusevm bytecode disassembly listing for
.I FILE
(the main chunk, every user function's chunk, and every try block) and exit,
instead of running it.
.TP
.B \-h, \-\-help
Print help and exit.
.TP
.B \-V, \-\-version
Print version and exit.
.SH ARGUMENTS
.TP
.I FILE
The
.I .js
script to run. Omit it to read from standard input (a terminal starts the REPL), or when
.B \-e
is given. A lone
.B \-
also selects standard input.
.TP
.I ARGS
Trailing arguments passed through to the JavaScript program.
.SH EXIT STATUS
Exits 0 on success, or with \fIprocess.exitCode\fR if the program set one. On error, a terse
.RB \(dq node:\ <reason> \(dq
message is written to standard error and the exit status is 1 (an uncaught
exception exits 1 unless an \fIexit\fR listener assigns another code).
.SH EXAMPLES
Evaluate a one\-liner:
.PP
.RS
.EX
node \-e 'console.log(1 + 1)'
.EE
.RE
.PP
Run a script file:
.PP
.RS
.EX
node app.js
.EE
.RE
.PP
Pipe a script over standard input:
.PP
.RS
.EX
echo 'console.log("hi")' | node
.EE
.RE
.SH SEE ALSO
Project home: <https://github.com/MenkeTechnologies/node-js>