---
url: /docs/5.x/reference/diagnostics/kubb-lint-failed.md
description: >-
  The KUBB_LINT_FAILED diagnostic fires when the linter pass over the generated
  files fails.
---

# KUBB\_LINT\_FAILED: Lint failed

Code: `KUBB_LINT_FAILED`
Level: error

The linter pass over the generated files failed. Linting runs after generation. The files are written, but the run is marked failed.

## What happened

When `output.lint` is set, Kubb runs the configured linter (oxlint, biome, or eslint) over the output directory. A non-zero exit from the linter shows up here, in the summary, and in `--reporter json`. Earlier versions swallowed it.

## How to fix it

* Confirm the linter is installed and its config is valid.
* Run it manually on the output to see the underlying error, for example `oxlint ./src/gen`.
* Relax the rules for generated files, or remove `output.lint` if you do not want a linter pass.

## Common causes

* The linter is not installed in the project.
* The linter config is invalid or points at a missing file.
* Lint rules flag the generated code as errors.

## Example output

```text [Terminal]
[KUBB_LINT_FAILED]: linter failed: Cannot find module 'oxlint'
  fix: Check that the tool is installed and that the command and its config are correct.
  see: https://kubb.dev/docs/5.x/reference/diagnostics/kubb-lint-failed
```

## See also

* [Configuration](/docs/5.x/reference/configuration)
* [`KUBB_FORMAT_FAILED`](/docs/5.x/reference/diagnostics/kubb-format-failed)
* [Diagnostics reference](/docs/5.x/reference/diagnostics)