`@pulse-compute/assets`#

@pulse-compute/assets is the supported application entry point for both direct JavaScript execution and supported Native lowering.

The package root exposes the complete JavaScript asset implementation—local files, hosted origins, S3-compatible buckets, and SigV4 support—plus the narrow request-bound surface that Native compilation can recognize.

Install#

npm install @pulse-compute/assets@1.0.0-beta.1

Portable lookup surface#

import { assets } from '@pulse-compute/assets'

const found = await assets.lookup(ctx, 'public', '/app.js', {
  method: 'GET',
  cacheControl: 'public, max-age=60',
})

return assets.respond(found)

The portable surface is:

assets.lookup(ctx, store, key, options?) — a request-bound package effect that may be directly awaited or used inside ctx.parallel({ ... });
assets.respond(response, options?) — a pure response-adoption and decoration helper;
equivalent named exports lookup and respond.

JavaScript executes the real package implementation through the request-owned package-effect bridge. Native compilation recognizes the same package-root call and emits the canonical assets.lookup package effect. Supported Native argument restrictions are enforced by package lowering eligibility and diagnostics rather than by changing the JavaScript API.

JavaScript middleware#

The package root also exports:

import {
  AssetManager,
  AssetBucket,
  createAssets,
  signSigV4,
} from '@pulse-compute/assets'

createAssets() supports local, hosted, and bucket-backed middleware. Hosted and bucket responses adopt upstream Web streams directly, preserving status, headers, and host-owned response-body ownership. Local assets currently follow the restored implementation and materialize the selected file. Broader request/response resource limits belong at a shared core ownership boundary rather than in an Assets-only policy.

Response ownership#

A direct asset response preserves:

status, including range responses such as 206;
repeated and ordinary headers;
GET and HEAD behavior;
upstream Web stream identity for hosted and bucket modes;
cancellation of discarded upstream bodies during pass-through or bodyless responses.

The portable response is opaque to Native application code. Structured request-body and fetched-response projection bounds remain separate core contracts.

Compatibility subpath#

@pulse-compute/assets/pulsewasm remains a compatibility subpath. New applications should import from @pulse-compute/assets. The manifest and compiler subpaths are trusted toolchain integration, not application APIs. See Compatibility imports and migration.

Package-owned files#

The release tarball includes:

the built JavaScript implementation and type declarations;
pulse.package.json product and target metadata;
pulsewasm.manifest.cjs trusted package-lowering identity;
pulsewasm.compiler.cjs package-specific static validation and lowering;
as/index.as.ts sidecar declarations used by compiled-Wasm integration.

See Package-owned lowering and Add a first-party package-owned lowerer.

@pulse-compute/assets#