Skip to content
Browse documentation
guides

Local development

Install retained packages and run native development without a second application runtime.

Use the adopted project's toolchain

Start in your created application's root. Smoothie Starter pins Bun 1.4.2 and Node 24; its native manifest and retained README describe the rest of the toolchain. Prepared Framework archives do not require building the SDK first.

bash
smoothie project context --format json
bun install --frozen-lockfile --ignore-scripts

Use the frozen install after the application's first install has generated bun.lock. For a newly created project with no lockfile, run bun install --ignore-scripts instead, review the generated lockfile, and retain it. Missing vendor archives are not repaired by rebuilding the SDK or acquiring a newer release automatically.

Start native development

bash
bun run dev

In Smoothie Starter this runs the server and browser development processes through the project's scripts. Use the addresses printed by the native tools. The production-like bun run build followed by bun run start serves the built app at http://127.0.0.1:42741; it is a different path from the development server.

Edit browser interface code under targets/web/src/, endpoint behavior under targets/server/, and shared request/response shapes under shared/contracts.ts. Use the selected renderer's native hooks and lifecycle. Styles compile through the project's existing Whisk Styles configuration; no browser-side style compiler or Smoothie development daemon is needed.

Start only the services your Recipe needs

The base web Starter needs neither a model provider nor a database. Interactive Agent needs its server-side model configuration for live messages. Durable Worker needs Redis, Postgres, migrations, and separately owned API/Worker processes. Follow that Recipe's README; do not apply the web Starter's commands as a universal service launcher.

Shut down owned resources through their native entrypoints. Development servers, detached processes, containers, and external services are not supervised by a long-running CLI session. A native check script must await the work it needs to complete.

Check before handing off

bash
smoothie project check
smoothie project verify
smoothie project verify --task typecheck --task test --run

Task discovery is non-executing; --run explicitly authorizes the selected scripts. Record failures and missing service prerequisites rather than replacing them with an empty test. See Testing and verification for browser and deployment checks, or coding-agent setup for release-matched skills and scoped context.