nx-config-cache-check

To detect misaligned Nx cache inputs and outputs, validate diffs to project.json, package.json targets, and nx.json targetDefaults. This surfaces cacheability conflicts, overlapping outputs, and sandbox violations to prevent stale cache restores during PR reviews.

Nx cache restores stale outputs when namedInputs or targetDefaults changes propagate misconfigurations. If cacheable targets do not declare accurate inputs or use dependentTasksOutputFiles for dependency outputs, the cache hash fails to capture relevant source file changes.

Validate Nx targetDefaults changes by checking that cacheable targets declare accurate inputs and outputs. Ensure dependentTasksOutputFiles properly captures dependency outputs, and flag any targetDefaults modifications that might introduce cacheability conflicts or sandbox violations across the workspace.

Yes, you can use Nx cache config validation for pre-push checks. It surfaces actionable recommendations by detecting overlapping outputs between targets and dependencies, ensuring inputs cover all source files affecting outputs before changes are merged.

The best way to prevent overlapping outputs is to ensure cacheable targets declare accurate inputs and outputs, utilizing dependentTasksOutputFiles for dependency outputs. Validating nx.json targetDefaults and namedInputs helps identify and resolve cacheability conflicts.