Skip to main content
Run each selected workspace member’s lint script and report which modules are clean. The command is standalone and caches each module’s lint result independently.

​
Usage

​
Examples

Lint every workspace member that has a lint script:
Lint selected names:
Show failed module output in the report:
Force every selected lint to run again:
Run linting from another workspace directory:

​
Options

​
Execution

lint discovers workspace members under modules/ and packages/, filters by the names passed through --modules and --packages, and selects members with a package.json that declares a lint script. Members without a package.json or without a lint script are skipped. Each runnable member executes bun run lint in its own directory. The run uses the machine’s available parallelism, capped at 8 workers. If any module fails or cannot run, the command exits with code 1.
workspace:run --commands=lint delegates to this standalone command, so the cache and behavior match talos lint.

​
Caching

Lint entries live in var/cache/lint/<module>.json. A module can replay from cache when the root lint inputs, the module itself, and every transitive workspace dependency still match the stored fingerprints. The cache stores completed passed and failed lint results, including output for --logs. A lint that could not be run is not stored. Pass --no-cache to bypass both reads and writes.

​
Output

The command prints a Lint report with one row per module that ran or replayed from cache. Cached rows are marked cached. Failed or errored modules appear under Failing modules; use --logs to include the last 40 non-empty output lines.