Implementation packages#

These packages are synchronized parts of the release set for compiler, provider, runtime, and package-lowering maintainers. They are not application-author SDKs.

The package status and supported entry-point lists below come from the synchronized Pulse 1.0.0-beta.1 release policy.

@pulse-compute/wasm-build-support#

Pulse release-set and compiler maintainers.

• Install directly: No for application projects; it is installed transitively where required.
• Stability: Internal release-set interface; exported modules may change with compiler implementation needs.

Supported entry points#

• None for application authors.

@pulse-compute/wasm-compiler#

Pulse compiler and release maintainers.

• Install directly: No for application projects; use the pulse CLI.
• Stability: Internal compiler interface; no application-author compatibility guarantee.
• Canonical replacement: @pulse-compute/cli

Supported entry points#

• None for application authors.

@pulse-compute/wasm-guest-link#

Pulse compiler, release, and first-party guest-unit maintainers.

• Install directly: No for application projects; it is an internal synchronized compiler dependency.
• Stability: Internal first-party prebuilt guest-link interface synchronized with the compiler; no application-author or third-party guest compatibility guarantee.

Supported entry points#

• None for application authors.

@pulse-compute/wasm-contracts#

Pulse compiler, runtime, provider, and package-lowering maintainers.

• Install directly: Provider toolchain authors may install it for the versioned bootstrap contract; application projects receive it transitively.
• Stability: The provider toolchain contract is versioned and supported for the Beta; other protocol and proof interfaces remain internal.

Supported entry points#

• @pulse-compute/wasm-contracts/provider/toolchain

@pulse-compute/wasm-host-runtime#

Pulse host-runtime and provider maintainers.

• Install directly: No for application projects; it is installed transitively.
• Stability: Internal compiler/runtime interface synchronized with this release set.

Supported entry points#

• None for application authors.

@pulse-compute/wasm-library-kit#

Pulse package-lowering and compiler maintainers.

• Install directly: No for application projects; it is installed transitively.
• Stability: Internal package-lowering interface synchronized with this release set.

Supported entry points#

• None for application authors.

@pulse-compute/provider-node#

Pulse canonical Node provider and compiler maintainers.

• Install directly: No for application projects; select provider: node through the CLI.
• Stability: The listed built-in toolchain entry is synchronized with the Beta bootstrap contract; other canonical Node provider interfaces remain internal.
• Canonical replacement: provider: 'node' through @pulse-compute/cli

Supported entry points#

• @pulse-compute/provider-node/toolchain

@pulse-compute/wasm-runtime-core-as#

Pulse AssemblyScript runtime-core and compiler maintainers.

• Install directly: No for application projects; it is installed transitively.
• Stability: Internal code-generation interface synchronized with this release set.

Supported entry points#

• None for application authors.

@pulse-compute/wasm-schema-json#

Pulse schema compiler and runtime maintainers.

• Install directly: No for application projects; declare schemas in the selected .pulse/config.ts profile.
• Stability: Internal schema compiler interface synchronized with this release set.
• Canonical replacement: schemas in .pulse/config.ts through the Pulse project workflow

Supported entry points#

• None for application authors.

Support boundary#

Only the entry points explicitly listed above carry the stated release promise. Exported implementation subpaths are not promoted into application-author APIs merely because npm can resolve them.