Package entry points

@viby/sdk publishes explicit entry points so portable application code does not accidentally load filesystem, process, PostgreSQL, Docker, browser-driver, or provider SDK dependencies.

Primary entry points

The portable core uses Web Request, Response, Headers, ReadableStream, AbortSignal, Uint8Array, text encoding, structured cloning, and Web Crypto-compatible shapes. It also includes pure product helpers such as titleFromPrompt() that do not require a model or runtime-specific APIs.

Storage and persistence

The S3 adapter requires optional peer @aws-sdk/client-s3.

Sandboxes

Provider SDK types stay inside their adapter configuration and never enter SandboxAdapter.

Browser and generation conformance

The Playwright adapter requires playwright; accessibility scans additionally use optional @axe-core/playwright.

Testing hosts and adapters

@viby/sdk/testing collects every public conformance suite behind one stable import and includes a queue-driven engine for deterministic API, worker, and UI tests:

import {
  createScriptedGenerationEngine,
  verifyPersistenceAdapter,
  verifySandboxAdapter,
} from "@viby/sdk/testing";

const scripted = createScriptedGenerationEngine({
  steps: [{ kind: "project", title, summary, files, usage, finishReason: "stop" }],
});

const viby = createViby({
  framework: "farmjs",
  generation: { engine: scripted.engine },
});

Each call consumes exactly one step. An unexpected extra attempt throws ScriptedGenerationEngineExhaustedError instead of inventing fallback output. calls, remaining, enqueue(), and clear() let tests assert retries and prepare later outcomes. Conformance suites may create external disposable resources; use dedicated test accounts and provider cleanup hooks.

Integration entry points

MCP entry points

Runtime rules

• Import types and Web helpers from @viby/sdk/core in portable/shared modules.
• Import the full client from @viby/sdk/node in new Node-only server code.
• Import providers only from their explicit subpaths.
• Install optional peers only for adapters the application actually configures.
• Do not deep-import files under dist; they are not part of the compatibility contract.
• Run the relevant conformance suite for every custom adapter implementation.

See Runtime boundaries for compatibility gates and supported runtimes.