1.0.0-beta.10 · latest
Package support policy
Source e69e4b6f1381 · Published v1.0.0-beta.10
Pulse 1.0.0-beta.10 publishes one synchronized 20-package release set. Publication does not make every package an application-author SDK: the support tier and listed entry points define the release promise.
Core packages
Section titled “Core packages”All short names below use the @pulse-compute/ npm scope. Full names and installation guidance are retained in the support contracts below.
| Package | Purpose | When to use |
|---|---|---|
pulse | Application root, config and schemas. | Start a Pulse project. |
cli | Project commands and build workflow. | Develop locally or run CI. |
runtime | Portable handlers, contexts and routers. | Type handlers and libraries. |
Capability packages
Section titled “Capability packages”Choose a package for the capability you need; its guide owns supported targets and limitations.
| Package | Purpose | When to use |
|---|---|---|
assets | Asset lookup and response delivery. | Serve files, origins or buckets. |
crypto | Signature verification and text digests. | Verify signatures or hash exact text. |
entities | Static, schema-backed entity dispatch. | Expose bounded JSON-RPC operations. |
grip | GRIP framing and broadcast effects. | Use an external Fanout gateway. |
jwt | JWT verification and token issuance. | Verify credentials or issue worker tokens. |
mcp | Bounded MCP HTTP host adapter. | Expose Entities tools to MCP clients. |
provider-fastly | Fastly configuration and target builds. | Run on Fastly Compute. |
s3 | Exact-key object reads and writes. | Access S3 through bounded effects. |
Implementation packages
Section titled “Implementation packages”These packages are mostly transitive implementation dependencies. Explicit supported entry points, including the Node provider's server entry, retain their documented exceptions; consult the implementation guide.
| Package | Purpose | When to use |
|---|---|---|
wasm-build-support | Shared build helpers. | Maintain package-owned builders. |
wasm-compiler | Native compiler implementation. | Maintain the compiler. |
wasm-guest-link | Guest-unit validation and Wasm linking. | Maintain first-party guest composition. |
wasm-contracts | Shared compiler and provider contracts. | Build toolchains or maintain protocols. |
wasm-host-runtime | Host builders and runtime helpers. | Maintain host execution. |
wasm-library-kit | Package lowerer and sidecar builders. | Maintain package lowering. |
provider-node | Node provider and HTTP launcher. | Serve Node builds or maintain the provider. |
wasm-runtime-core-as | AssemblyScript runtime generation. | Maintain Native runtime code generation. |
wasm-schema-json | Schema registry and codec builders. | Maintain schema compilation. |
Full support contracts, installation guidance, and npm links
| Package on npm | Guide | Support tier | Install directly | Release promise |
|---|---|---|---|---|
@pulse-compute/pulse | Guide | Canonical application surface | Yes. Install it in every conventional Pulse project. | Supported conventional application, project-configuration, and schema-authoring contract. |
@pulse-compute/cli | Guide | Canonical application surface | Yes. Install the package globally or as a project development dependency. | Supported Beta workflow and project-configuration contract. |
@pulse-compute/runtime | Guide | Canonical application surface | Yes. Install it in every Pulse application. | Supported application authoring and execution contract. |
@pulse-compute/assets | Guide | Supported provider/extension surface | Yes, only when the application uses the assets capability. | The package root is the supported JavaScript API and canonical Native authoring surface, including bounded embedded Assets bytes on their qualified targets. /pulsewasm remains a compatibility subpath; manifest/compiler subpaths are toolchain integration. No application binary inspection is exposed. |
@pulse-compute/crypto | Guide | Supported provider/extension surface | Yes, when an application uses verification or digestText directly; JWT applications receive it transitively. | The package root supports bounded verification and request-owned exact-text digests; provider, manifest/compiler and Native integration subpaths remain toolchain-only. |
@pulse-compute/entities | Guide | Supported provider/extension surface | Yes, when an application declares entity operations. | The package root and first-party JSON-RPC adapter are supported Beta contracts; compiler integration subpaths remain toolchain-only. |
@pulse-compute/grip | Guide | Supported provider/extension surface | Yes, only when the application uses GRIP/Fanout behavior. | The package root has bounded JavaScript and Native HTTP-framing realization plus configured Node/Fastly broadcast; /pulsewasm remains compatibility-only. |
@pulse-compute/jwt | Guide | Supported provider/extension surface | Yes, when an application verifies or signs JWTs. | The package root supports provider-neutral verification and bounded HS256/ES256/RS256 signing; provider and compiler integration subpaths are not application APIs. |
@pulse-compute/mcp | Guide | Supported provider/extension surface | Yes, for the host adapters or the static /pulse binding. | The root Fetch handler and /node HTTP bridge retain fixed-backend host behavior. /pulse supplies a static package-owned Native binding with local Entities dispatch, strict HTTP admission and no fallback. Protocol resources, prompts, sessions and stdio are unsupported. |
@pulse-compute/provider-fastly | Guide | Supported provider/extension surface | Yes, for Fastly projects. Node-only projects do not need to import it directly. | The listed entry points are supported for the Beta; all other exported subpaths are implementation-only. |
@pulse-compute/s3 | Guide | Supported provider/extension surface | Yes, when an application uses S3 object operations. | The package root supports head, getText, getBody and putText on Node Native, Node JavaScript and Fastly Native. getBody returns bounded opaque binary responses with the documented HTTP subset. Fastly JavaScript is ineligible. Provider and lowering subpaths are toolchain-only; live origin acceptance is separate. |
@pulse-compute/wasm-build-support | Guide | Implementation/transitive surface | No for application projects; it is installed transitively where required. | Internal release-set interface; exported modules may change with compiler implementation needs. |
@pulse-compute/wasm-compiler | Guide | Implementation/transitive surface | No for application projects; use the pulse CLI. | Internal compiler interface; no application-author compatibility guarantee. |
@pulse-compute/wasm-guest-link | Guide | Implementation/transitive surface | No for application projects; it is an internal synchronized compiler dependency. | Internal first-party prebuilt guest-link interface synchronized with the compiler; no application-author or third-party guest compatibility guarantee. |
@pulse-compute/wasm-contracts | Guide | Implementation/transitive surface | Provider toolchain authors may install it for the versioned bootstrap contract; application projects receive it transitively. | The provider toolchain contract is versioned and supported for the Beta; other protocol and proof interfaces remain internal. |
@pulse-compute/wasm-host-runtime | Guide | Implementation/transitive surface | No for application projects; it is installed transitively. | Internal compiler/runtime interface synchronized with this release set. |
@pulse-compute/wasm-library-kit | Guide | Implementation/transitive surface | No for application projects; it is installed transitively. | Internal package-lowering interface synchronized with this release set. |
@pulse-compute/provider-node | Guide | Implementation/transitive surface | Yes for the production Node launcher; application handlers remain provider-neutral. | 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. |
@pulse-compute/wasm-runtime-core-as | Guide | Implementation/transitive surface | No for application projects; it is installed transitively. | Internal code-generation interface synchronized with this release set. |
@pulse-compute/wasm-schema-json | Guide | Implementation/transitive surface | No for application projects; declare schemas in the selected .pulse/config.ts profile. | Internal schema compiler interface synchronized with this release set. |
Tier definitions
Section titled “Tier definitions”Canonical application surface
Section titled “Canonical application surface”Fully documented and supported as the Pulse application authoring or workflow contract.
Supported provider/extension surface
Section titled “Supported provider/extension surface”Documented entry points are supported; implementation and toolchain subpaths are explicitly excluded.
Implementation/transitive surface
Section titled “Implementation/transitive surface”Installable as part of the synchronized release set. Only explicitly listed supported entry points carry their stated compatibility guarantee; all other interfaces are internal.
Reading package READMEs
Section titled “Reading package READMEs”Every packed README begins with a generated status block covering audience, direct-install guidance, supported entry points, and stability. An export that is not listed in that block is not automatically a supported application-author entry point.
Extension and provider boundary in 1.0.0-beta.10
Section titled “Extension and provider boundary in 1.0.0-beta.10”Package roots are the application APIs. Older Assets and GRIP /pulsewasm imports remain bounded migration surfaces.
Package-owned lowerers may come from external packages under the versioned contract. They execute as trusted build dependencies with the compiler process's authority, without a sandbox. Reachable imports select declared lowerers; package ownership, protocol validation and provider capability checks still apply. No publisher allowlist or matching compiler release version is required.
Providers are explicitly selected by a bare host ID or exact scoped package name and must export the versioned ./toolchain contract. Bare IDs use the @pulse-compute/provider-<id> convention; none is compile-only. There is no scanning, self-registration or fallback. See the current provider contract.
Installed documentation
Section titled “Installed documentation”@pulse-compute/runtime ships its canonical API reference and Beta scope. @pulse-compute/cli ships the public documentation hierarchy, CLI/config/diagnostic references, bounded compatibility material, and runnable example sources. Package README links must resolve either inside their own tarball or to an exact-version hosted Pulse documentation URL.