Phase 61

Node.js

Node.js runs natively inside m3OS with the documented level of runtime and networking support, and npm can install the packages needed by the later CLI-agent phase.

Planned

Learning goal

Understand how JIT-heavy or managed runtimes stress memory, mapping, and execution permissions differently from simpler binaries.

Why this phase matters

Node.js runs natively inside m3OS with the documented level of runtime and networking support, and npm can install the packages needed by the later CLI-agent phase.

How it works in m3OS

The roadmap entry defines the learning scope for this phase; a deeper implementation doc has not been matched yet.

How it builds on earlier phases

This phase builds on Networking And GitHub and turns that foundation into Node.js.

Implementation outline

Choose the supported Node.js configuration and document the non-goals.
Bring up the local runtime behavior first.
Add the documented networking and npm path needed for later CLI-agent work.
Validate the runtime against the supported use cases.
Update docs and standalone Node roadmap material to match the official milestone.

Task progress snapshot

No checklist tasks were discovered for this phase yet.

Documentation targets

Documentation deliverables have not been listed yet.

Deferred follow-on work

Native addon and node-gyp support
Full developer-inspector integration
Rich multi-runtime JS workflows beyond the documented support set
Broader desktop-oriented Node application ecosystems

Source materials

Roadmap entry

Important code

Code spotlight cards

When the phase lands, bump kernel/Cargo.toml and any release/version references to 0.61.0.

View on GitHub

Key files

kernel/Cargo.toml — When the phase lands, bump kernel/Cargo.toml and any release/version references to 0.61.0.

How real OSes differ

Mature systems support far broader Node workflows, native addons, inspection tooling, and ecosystem assumptions than m3OS needs here.
The goal is not to replicate every Linux/npm expectation; it is to support the subset needed by the planned post-1.0 platform story.
Support boundaries matter especially with large runtimes because ecosystem assumptions expand faster than kernel capability.

Success criteria

Node.js runs the documented local runtime workloads inside m3OS.
The documented networking-dependent Node workloads and package-install path also work.
npm or the chosen equivalent package path is usable for the later CLI-agent milestone.
The phase docs clearly describe what Node support exists and what remains unsupported.
The runtime configuration and install layout are reproducible through the documented build flow.

Related phases

Keep exploring the roadmap

Networking And GitHub

m3OS can use authenticated outbound network tooling for real developer workflows: DNS works, HTTPS is trustworthy enough for the supported use cases, git can speak to remotes, and the GitHub CLI runs inside the OS.

Claude Code

Claude Code runs natively inside m3OS, using the supported Node, network, git, and GitHub tooling to read code, run commands, and participate in the same developer workflow the earlier post-1.0 phases made possible.