node-js 0.1.13

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 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

//! Ahead-of-time compilation (`node --build`).
//!
//! Precompiles the script to fusevm bytecode, warms the on-disk cache
//! (`cache.rs`) so subsequent runs skip lex/parse/lower, and — via fusevm's `aot`
//! feature (a native-object emitter linked against the node-js `staticlib`) —
//! emits a standalone native executable that carries the node-js builtin dispatch
//! and the fusevm AOT runtime. The report below is explicit user-requested
//! output.

/// Precompile `file` to a standalone native executable next to the source, and
/// warm the bytecode cache. Returns a one-line report of what was built.
pub fn build(file: &str) -> Result<String, String> {
    let src = std::fs::read_to_string(file).map_err(|e| format!("cannot read {file}: {e}"))?;
    let prog = crate::compile(&src)?;
    let (nfns, nops) = (prog.functions.len(), prog.main.ops.len());
    crate::cache::store(&src, &prog)?;
    // `--build` warms the shard for later runs, so it must reach disk here
    // rather than at the end of an ordinary run.
    crate::cache::flush();

    // Emit the native object + link a standalone executable. The output path is
    // the source stem (`foo.js` -> `foo`).
    let stem = std::path::Path::new(file)
        .file_stem()
        .map(|s| s.to_string_lossy().into_owned())
        .unwrap_or_else(|| "a.out".into());
    let out = std::path::Path::new(file)
        .parent()
        .unwrap_or_else(|| std::path::Path::new("."))
        .join(&stem);
    crate::aot_native::emit_executable(&prog, &out)?;

    Ok(format!(
        "built {file}: {nops} top-level ops, {nfns} functions -> {} (+ ~/.node-js/scripts.rkyv)",
        out.display()
    ))
}