You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A solution - if implementation should be untouched - can be a plugin which adds a pseudo build target to every project and reference this name in the eslint rule config for @nx/dependency-checks. A working example can be found in the repo specified above:
RobbyRabbitman
changed the title
docs: @nx/dependency-checks cannot handle different build target names of when resolving project dependencies
docs: @nx/dependency-checks cannot handle different build target names when resolving project dependencies
Dec 20, 2024
Current Behavior
@nx/dependency-checks
resolves projects dependencies via the exact target name of its build target name. This is only documented as a TODO in https://github.com/nrwl/nx/blob/19b0828d278b5fa8e3d9f8fc537b317c7f442848/packages/eslint-plugin/src/rules/dependency-checks.ts#L145C7-L145C96Expected Behavior
Add docs.
GitHub Repo
https://github.com/RobbyRabbitman/cv/tree/nx-dependencies-checks-issue-2
Steps to Reproduce
nx-dependency-checks-issue.sh
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
A solution - if implementation should be untouched - can be a plugin which adds a pseudo build target to every project and reference this name in the
eslint
rule config for@nx/dependency-checks
. A working example can be found in the repo specified above:https://github.com/RobbyRabbitman/cv/blob/3a5a34c13630adbaedae08b6727a1230d7dd7831/nx.json#L130-L132
https://github.com/RobbyRabbitman/cv/blob/3a5a34c13630adbaedae08b6727a1230d7dd7831/tools/eslint/src/eslint.config.nx.ts#L11-L36
https://github.com/RobbyRabbitman/cv/blob/3a5a34c13630adbaedae08b6727a1230d7dd7831/tools/nx-eslint-dependency-checks-plugin/src/nx-eslint-dependency-checks-plugin.ts#L17-L55
The text was updated successfully, but these errors were encountered: