@pulse-compute/provider-node

Support tier: Implementation/transitive surface Audience: Node deployment integrators and Pulse provider maintainers. Install directly: Yes for the production Node launcher; application handlers remain provider-neutral. Supported entry points: @pulse-compute/provider-node/toolchain, @pulse-compute/provider-node/server Stability: The /server export is an explicit supported-entry-point exception within this implementation package: finite production HTTP for explicit Node Native and JavaScript builds. Forwarding, generated output, transforms, S3-body bindings and blob-specific production qualification remain separate. /toolchain serves the CLI; all other provider subpaths remain internal. npm: @pulse-compute/provider-node Canonical documentation: Package guide

This release-status block is generated from the synchronized Pulse 1.0.0-beta.9 package policy.

Canonical Node provider implementation used internally when a project selects provider: 'node'.

Deployment integrators install this package and import @pulse-compute/provider-node/server to launch a trusted pulse build directory. Application handlers remain provider-neutral. See Node build and execution for configuration, readiness, drain, signals and restart.

Responsibilities

• declare the Node canonical provider descriptor and capability mappings;
• execute canonical programs through the Node local/runtime path;
• realize fetch, config, secret, KV, structured response, opaque pass-through, supported package effects, and invocation-scoped event ingress/acceptance;
• normalize provider failures into canonical runtime diagnostics;
• supply compiler/runtime proofs for maintained internal lifecycle surfaces.

Boundaries

• Canonical handlers never receive Node request/response objects or ambient process authority.
• Package-specific payload rules remain in their owning package/contracts.
• Product command behavior remains in the CLI package.
• JavaScript execution remains an explicitly selected Node target and never an automatic fallback.
• Event ingress is a bounded FIFO reference adapter with one active invocation per instance; outbound acceptance is a separate exact-frame ledger with no loopback, delivery, retry, persistence, or process-global singleton.

JavaScript application host boundary

The provider-maintainer JavaScript subpaths are:

@pulse-compute/provider-node/javascript/target
@pulse-compute/provider-node/javascript/runtime-host
@pulse-compute/provider-node/javascript/node-adapter
@pulse-compute/provider-node/javascript/lifecycle

The graph-backed loader, Web request/response adapter, provider-owned pulse dev lifecycle, capability adapters, schema codecs, Assets, and bounded GRIP behavior are maintained under the target-support and cross-target conformance contracts. No automatic fallback occurs, and application projects do not import these implementation subpaths directly.

The Node JavaScript provider also realizes canonical pulse.jwt verification through the package-owned jose/Web Crypto verifier. It owns named-secret resolution and wall-clock capture; applications cannot select a crypto backend.

Implementation exports

The package exposes focused compiler and runtime modules for the synchronized repository, including runtime/canonical-api-runtime. Those exports are implementation interfaces, not application-author APIs.

See Contracts and providers and Implementation packages.