New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linting --with-deps does not work on Nx 12.8 #6922
Comments
Does anyone know why --with-deps is deprecated? I don't see any other way to do it like --with-deps |
@maxisam Its being deprecated because now you can define targetDependencies. You can read more about it at https://nx.dev/l/r/core-concepts/configuration and under the Target Dependencies section. |
@nelsond6 The funny thing is I use the targetDependencies way, and it still throws the same error. I am on 12.10.0 Node : 14.18.1 nx : 12.10.0 |
@maxisam - yeah it did the same for me. Both --with-deps or using targetDependencies ends up in the same error. The good news is this is fixed in NX 13! |
I still get this error with https://github.com/ionic-team/stencil-eslint extension with stencil-library setup in nx. Had to install with Now I get Invalid lint configuration. Nothing to lint. Please check your lint target pattern(s).
Error: Invalid lint configuration. Nothing to lint. Please check your lint target pattern(s).
at /Users/pranav.sarda/Documents/GitHub/zwitch-frontend/packages/linter/src/executors/eslint/lint.impl.ts:98:11
at Generator.next (<anonymous>)
at fulfilled (/Users/pranav.sarda/Documents/GitHub/zwitch-frontend/node_modules/tslib/tslib.js:114:62) |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Current Behavior
Linting a project and all its dependencies does not work.
Expected Behavior
Linting a project and all its dependencies should work. I believe this is a regression. Even if --with-deps is deprecated, it should still work until Nx 14.
Steps to Reproduce
yarn
yarn nx lint cart --with-deps
This issue may not be prioritized if details are not provided to help us reproduce the issue.
Failure Logs
Environment
The text was updated successfully, but these errors were encountered: