Skip to content

Proposal: --filter no-match should not fail by default; add --fail-if-no-match for strict mode #380

@branchseer

Description

@branchseer

vp run --filter {.}^... build fails when the filter matches no packages (e.g. a leaf package with no workspace deps). For traversal filters that exclude the seed, zero matches is a legitimate outcome, not a typo.

Proposal: match pnpm's behavior — treat no-match as success by default, and add --fail-if-no-match for callers (CI, scripts) that want strict behavior.

For reference, pnpm exits 0 on no-match and supports --fail-if-no-match (and a failIfNoMatch setting) to opt into failure: https://pnpm.io/filtering

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions