This guide explains how to exclude paths from a Vibgrate scan using the --exclude flag so generated, vendored, or irrelevant directories do not skew your results. It is for developers who want a scan focused on the code they actually own.
Overview
Not every folder in a repository is worth scanning for upgrade drift. Build output, vendored third-party copies, fixtures, and generated code can add noise. The --exclude flag tells the Vibgrate CLI to leave those paths out.
Step-by-step
Exclude a directory from the scan:
vg scan --exclude dist
Exclude generated or vendored folders so they do not affect the DriftScore:
vg scan --exclude generated
When to exclude
- Build and distribution output that is not source you maintain.
- Vendored copies of dependencies that you do not upgrade directly.
- Large fixture or sample directories that are not part of the shipped application.
For durable, project-wide exclusions you should put them in your configuration file rather than passing the flag on every run. See the configuration reference for setting exclusions in vibgrate.config.ts.
Related
See the configuration reference, the scanning a monorepo guide, the scanning large repositories guide, and the scan command reference.