Ignoring specific warnings

[PatrykKuniczak]

Summary

Currently, TurboRepo logs all warnings to the console, which can clutter the output when certain warnings are unnecessary or irrelevant for a specific workflow.
For example, when setting daemon: false in the configuration, the warning daemon is required for watch, ignoring request to disable daemon for turborepo is displayed.
In some cases, this warning is expected, and its repeated appearance can make the logs harder to read, especially in CI/CD environments or when debugging other issues.

Additional information

Proposed Solution

1. Introduce a feature that allows users to suppress specific warnings by:

Providing an option in the configuration file (e.g., turbo.json) to ignore specific warnings by their content or a warning code.

{
  "suppressWarnings": [
    "daemon is required for watch"
  ]
}

2. Introduce structured warning codes to make suppression easier and more explicit.

npx turbo run <task> --suppress-warning-code="TURBO001"
or by message:
npx turbo run <task> --suppress-warning="daemon is required for watch"

This feature would be particularly useful in scenarios where warnings are acknowledged but not actionable, such as enforced behaviors (daemon: false in watch mode) or specific environment configurations (e.g., CI pipelines).

Suppressing these warnings without suppressing all logs or warnings entirely (via --quiet) would provide a more granular control over logging behavior.

[anthonyshew]

It doesn't sound like this covers everything you're looking for, but many messages can be suppressed with environment variables: https://turbo.build/repo/docs/reference/options-overview#messages

[PatrykKuniczak]

I'll try to solve my issue with this, but are you able and eager to implement dedicated solution for cases like mine?

[anthonyshew]

I would say that this is a good idea but won't make it to being high priority for us unless this Discussion starts collecting many upvotes or lots of activity.