Node
The Node platform provides focused adapters for Node-specific, non-isomorphic APIs.
Overview
Section titled “Overview”Node adapters are:
- Focused - Specific adapters for specific Node APIs (no generic
@xmachines/nodepackage) - Optional - Only install what you need
- Web Streams first - Web Streams remain the canonical API
- Interop only - No execution semantics or protocols
Available Adapters
Section titled “Available Adapters”@xmachines/node-stream
Section titled “@xmachines/node-stream”Adapters between Node streams and Web Streams.
@xmachines/node-process
Section titled “@xmachines/node-process”Process management and lifecycle hooks.
Installation
Section titled “Installation”# Install specific adapternpm install @xmachines/node-stream
# Or install bothnpm install @xmachines/node-stream @xmachines/node-processCore Principles
Section titled “Core Principles”1. Web Streams Are Canonical
Section titled “1. Web Streams Are Canonical”Node adapters bridge to Web Streams - they don’t replace them.
2. Optional Adapters
Section titled “2. Optional Adapters”Node adapters are opt-in. The core runtime works in Node without any Node-specific packages.
3. No Protocol Semantics
Section titled “3. No Protocol Semantics”Adapters provide raw interoperability. They don’t define protocols or execution patterns.
Usage Examples
Section titled “Usage Examples”Coming soon - examples for stream and process adapters will be added as the packages are implemented.
Learn More
Section titled “Learn More”- RFC: Node v1 - Technical specification
- Platform Overview - Other platform options
- Core Concepts - XMachines fundamentals