Skip to content
Browse documentation
start here

Compatibility and release scope

Check the TypeScript toolchain, tested hosts, rendering limits, and what verification results prove.

Release scope

These guides target public CLI 0.0.17 and TypeScript Framework 0.1.0. Smoothie Framework 0.1.0 is pre-release: commercial approval and production support are pending. A passing integrity check confirms that files match their release records; it does not prove who published them or that the release is production-ready. Successful local tests do not establish compatibility with every provider. Other language SDKs are outside this release's support scope.

bash
smoothie --version
smoothie project context --format json

Run project context inside a created application to see the exact Framework release it retains, including its exact release tag and revision. The CLI, the Framework, third-party packages, and machine-readable schemas are versioned separately. Every Framework package reports version 0.1.0, so the package version alone does not identify the exact release you have.

Toolchain

ApplicationSmoothie Starter with Bun 1.4.2, Node 24, and a root package.json.
Browser buildOctane 0.13.8, its TanStack Router binding 0.2.10, and Vite 8.3.2.
Octane compiler@tsrx/oxc 0.20.0.
Formatting and lintBiome 2.5.15, configured by the Starter's biome.jsonc.
TypeScriptTypeScript 7.0.2 checks the application through the typescript-check alias; Octane's compiler uses TypeScript 5.9.3.
Adding packages to an existing projectA single Bun project with an exact packageManager pin. Bun or npm workspaces and bun.lockb are not supported.

Use the package.json and bun.lock supplied by your Starter; older releases can pin different versions. Do not replace the ordinary typescript dependency with TypeScript 7: Octane's compiler needs 5.9.3. Other Starters may need additional services or hosts; follow their own README rather than this web Starter's assumptions.

Tested hosts

macOS ARM64Native tests and installer checks passed for 0.0.17.
Linux x64Native tests and installer checks passed for 0.0.17.
macOS x64Native Intel qualification passed, including the relocated archive and installer.
Linux ARM64Native qualification passed, including the relocated archive and installer.
Windows x64Native executable and PowerShell installer qualification passed. Separate post-publication installation was not rerun; native project checks remain unavailable.

A published archive is not the same as fresh native qualification. The local tutorial runs a long-running Bun and Elysia server. Smoothie Starter also includes an optional Cloudflare target; its presence does not qualify other hosts, Starters, features, or remote deployment workflows.

Rendering mode

The first application renders in the browser only; server-side rendering is not part of this path. Octane and React each have their own SSR status and known limitations. Read the Octane or React adapter documentation before choosing SSR, and do not infer SSR support from a passing client-rendered Starter.

Octane 0.13.8 has a hydration limitation when mapped children contain literal empty text: hydration can replace server-rendered nodes and lose focus or text selection. Avoid that pattern in SSR views, or render the affected view only on the client. Upgrading to 0.14.1–0.14.3 does not resolve it. Test SSR node reuse and input state in your own views before changing the pinned version.

What verification proves

A successful command proves only what it ran

Metadata checks do not run application code. Project scripts are your application's code: the CLI runs them without a sandbox, and a passing script can still skip tests internally. A submitted deployment is not proof of a healthy application. A passing integrity check confirms that files match their release records; it does not prove who published them or that the release is production-ready. Keep diagnostics and test the behavior your product needs.