Skip to content
Sarj Repo Standards
core/migration/tracked-install-artifacts

Do not track Node install artifacts during migrations

A tree with declared migrations does not track node_modules files or Yarn install state.

warning beta

Examples

FlaggedFails
applications/alpha/api/pyproject.toml
node_modules/example/index.js
.yarn/install-state.gz
PassesClean
applications/alpha/api/pyproject.toml
package-lock.json
.gitignore

Why it matters

Generated, machine-specific install state can dominate review and CI inputs.

How detection works

When a migration is declared, reports tracked .yarn/install-state.gz files and files beneath any node_modules directory as one repository-level finding.

What is inspected

  • Tracked paths from the exact selected Git tree.

Limits

  • Rejecting committed dependency lockfiles.
  • Reading untracked worktree files.
  • The rule recognizes only node_modules paths and .yarn/install-state.gz, and runs only when a migration is declared.

How to fix it

Remove generated installation outputs from the selected tree.

  1. Untrack node_modules trees and Yarn installation state.
  2. Add or repair ignore rules before reinstalling from the lockfile.

Verify

  • Inspect the exact committed tree and rerun repo-lint check.