Upgrading

Tavo.js Framework 1.0 establishes the stable baseline. Read the Core and UI release notes for every version crossed, including configuration, generated-artifact, runtime, and experimental-API changes.

Core publishes machine-readable stable and experimental labels from @tavojs/core. Stable entry points follow semantic versioning from 1.0 onward; experimental entry points may evolve more quickly.

Check npm outdated and review the release notes before running these commands: @latest can include a new major version. Keep @tavojs/core, @tavojs/cli, and @tavojs/ui on compatible releases; their version numbers do not need to be identical. The generated application installs @tavojs/cli as a development dependency and exposes its project-local tavo binary. The tavo-ui command is supplied through @tavojs/ui; do not install or upgrade @tavojs/ui-cli separately.

• With pnpm, add @tavojs/core and @tavojs/ui, then add @tavojs/cli with --save-dev.

• With Yarn, add the same three package names and keep @tavojs/cli in devDependencies.

• With Bun, add the same three package names and keep @tavojs/cli in devDependencies.

• Commit the manifest and lockfile together so CI and contributors install the reviewed dependency graph.

bashnpm install @tavojs/core@latest @tavojs/ui@latest
npm install --save-dev @tavojs/cli@latest

Build once with the project-local CLI after installation so generated route types and manifests use the same version that will ship. Then diagnose the result. Treat doctor suggestions as reviewable changes; doctor --fix-dry-run reports proposed low-risk fixes without editing files.

bashnpx tavo build
npx tavo doctor --fix-dry-run
npx tavo check
npx tavo routes
npx tavo-ui web check

Use the test runners already configured in the application; the Playwright command below assumes it is installed and has tests. Typecheck and test the application, then create a production report and exercise the SSR output in a browser. Give extra attention to routing, hydration, actions, caching, error boundaries, theme output, and any API called out by the release notes.

• Compare bundle reports and route manifests with the previous release when performance or static output is contractual.

• Run npx tavo preview --ssr in a separate terminal and smoke-test direct production-rendered requests before release.

• Deploy through the normal staging path and verify the generated output, secrets, caches, sessions, and monitor endpoint.

• Keep the previous lockfile and deploy artifact available until the new release passes production smoke checks.

bashnpx tsc --noEmit
npx tavo build --report-json
npx tavo verify --smoke --json
npx playwright test