feat: add devDependencies support & regex ignored dependencies to @nx/dependency-checks

[nwidynski]

This (non-breaking) PR adds support for multiple configuration objects as well as a production flag to the dependency-checks eslint rule. This is similar to how https://knip.dev/features/production-mode works.

With this change, it is now possible to enforce presence of devDependencies for dev-only files, e.g. .spec, like so:

// ...
"@nx/dependency-checks": ["error", 
  { "ignoredFiles": ["**/*.spec.ts"] }, 
  { "production": false, "ignoredFiles": ["**/!(*.spec.ts)"] }
]

Furthermore, this PR also adds capability to match dependencies via regex pattern in the ignoredDependencies.

Current Behavior

It is impossible to enforce dev-only dependencies.

Expected Behavior

Related Issue(s)

Fixes #30614

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Apr 8, 2025 9:41pm

[nwidynski]

@FrozenPandaz Any updates here?

[leosvelperez]

Thanks for contributing!

Some general feedback:

• Look for operations that could be cached for all visitors. For example:
  • The call to findNpmDependencies could be cached using buildTarget as the key, most of the time all configs will have the same buildTarget
  • The few Regex you added could be created once instead of every time they are needed
• Please do not remove existing comments unless you're addressing them or are outdated

[leosvelperez]

The current changes would allow multiple configurations with the same value for production and more than two configurations, which is not ideal. The tooling wouldn't prevent users from making such a mistake. We need to limit to at most two configurations, and a way to enforce that there are not two configurations with the same value for production.

Additionally, it would be great if users wouldn't have to repeat common configuration properties for both configurations.

[PowerSupply]

Any progress on this?

[nwidynski]

@PowerSupply Not for now, I will see whether I can pick this back up later this month.