Package scripts

dbx writes files, not your package.json — but a few scripts are worth standardizing, because the toolchain's formatting/linting and task running both go through Vite+. Any bare dbx <command> that matches a Vite+ command is forwarded straight to it (dbx fmt, dbx run -r build, dbx dev), so a project only needs the one dbx command. This page shows the recommended root scripts and how to move an existing Biome + Turbo project onto them.

Recommended scripts

The repo root package.json:

package.json

{
    "scripts": {
        "format": "dbx fmt",
        "lint": "dbx lint --fix",
        "check": "dbx check",
        "build": "dbx run -r build",
        "typecheck": "dbx run -r typecheck",
        "test": "dbx run -r test",
        "dbx:sync": "dbx sync",
        "dbx:watch": "dbx watch",
        "commitlint": "commitlint",
        "postinstall": "husky"
    }
}

Script	What it does
format / lint / check	Oxfmt / Oxlint across the repo (check = format check + lint).
build / typecheck / test	Runs the task in every workspace, in dependency order.
dbx:sync / dbx:watch	Regenerate the managed files / re-sync on change.
commitlint / postinstall	Conventional Commits via commitlint + husky.

Notes:

• A bare command that names a Vite+ command is forwarded to Vite+ (vp) — eg. dbx fmt, dbx dev, dbx run -r build, dbx add zod (Vite+ aliases too). Built-in commands win, so dbx migrate is the toolchain's migration — use dbx vite migrate for Vite+'s. The explicit dbx vite <command> passthrough always works.
• Vite+ resolves from the repo root, so format/lint live there — keep them out of the individual workspaces.
• dbx run -r <task> runs a task in every workspace package in dependency order. A task is either a package.json script or a vite.config.ts run.tasks entry. For long-running processes use dbx run -r --parallel dev.
• dbx is the toolchain binary, so yarn dbx <cmd> (eg. yarn dbx sync) works even without a script; the dbx:* aliases are just for discoverability.

When ci.changelog is enabled, dbx sync also writes a husky commit-msg hook (.husky/commit-msg) that runs commitlint, so commits are linted locally as well as in CI. Use postinstall (not prepare) to activate husky: Yarn Berry never runs prepare on install. Husky hooks have no file extension, so on Windows add .husky/* text eol=lf to .gitattributes — a trailing CR silently breaks the hook.

Migrate an existing project

1. Add the toolchain + Vite+, and drop what they replace:

   -    "@biomejs/biome": "catalog:",
   -    "turbo": "^2.11.2",
   +    "@deltabox/toolchain": "^1.2.3",
   +    "vite-plus": "^1.2.0",

2. Fold the Biome config into a root vite.config.ts:

   dbx migrate --from biome --target vite --write

   Or, if the project uses dbx.config.ts, author the Vite+ config there under toolchain.vite. dbx sync then writes the root vite.config.ts shim (see Vite+). dbx migrate --from vite --write folds an existing hand-written vite.config.ts in.

3. Replace the scripts (see the tables below), then delete biome.json and turbo.json.

4. Add a dbx.config.ts and sync the managed files:

   dbx sync

5. Verify — this is what CI runs:

   dbx sync --check
   yarn build

Biome → Oxc

Before	After
biome format --write .	dbx fmt
biome check --fix .	dbx lint --fix
biome.json	vite.config.ts

Remove @biomejs/biome, delete biome.json, and drop any per-workspace format/lint scripts.

Turbo → Vite Task

Before	After
turbo build	dbx run -r build
turbo typecheck	dbx run -r typecheck
turbo test	dbx run -r test
turbo dev	dbx run -r --parallel dev
turbo.json	(optional) run.tasks in vite.config.ts

Remove turbo and turbo.json. Ordering comes from each package's package.json dependencies, so no turbo.json graph is needed.

Per-workspace tasks

For cached, dependency-aware tasks, define them in each package's dbx.config.* rather than package.json — a task and a script cannot share a name:

packages/<pkg>/dbx.config.ts

import { defineConfig } from '@deltabox/toolchain';

export default defineConfig({
    toolchain: {
        vite: {
            run: {
                tasks: {
                    build: {
                        command: 'tsdown --config-loader unrun',
                        cache: { input: [{ auto: true }, '!dist/**'], output: ['dist/**'] },
                    },
                    test: {
                        command: 'vitest run',
                        cache: { input: [{ auto: true }], output: [] },
                    },
                },
            },
        },
    },
});

See the Monorepo guide for the full task setup, Migrations for the dbx migrate reference, and Providers (Vite+) for the dbx vite passthrough.