-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
cannot lint a brand new js lib #26755
Comments
Same issue here with a new React app. The issue could be in the eslint plugin function This essentially seems to render the ESLint integration useless for integrated monorepos. |
I believe this should have been corrected in the v14 release. Can you try again with latest? If its still failing, uploading a reproduction should help diagnose further. |
this still occurs on 19.4.1 as noted above. I hoped providing the 4 lines to paste into the terminal was good for providing a repro :) |
This issue has been automatically marked as stale because no results of retrying on the latest version of Nx was provided within 7 days. |
yes. Hi. on 19.4.3 the same steps to reproduce do still reproduce the errors mentioned |
Thanks for reporting this! This was fixed by #26638. Creating a new workspace with 19.4.4 or later now works as expected. If you already have a workspace created in an older version, please migrate to 19.4.4 or later to address the issue. |
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
My brand new workspace does not lint my brand new lib.
nx lint my-lib
saysCannot find configuration for task my-lib:lint
Expected Behavior
My lib would lint out of the box
GitHub Repo
No response
Steps to Reproduce
Nx Report
Failure Logs
Cannot find configuration for task my-lib:lint
Package Manager Version
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: