-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
v19.8.3 - Expected an assignment or function call and instead saw an expression #28245
Comments
@jaysoo I see this issue with react workspace too
/Users/s.yadav/react-india/libs/my-awesome-lib/package.json I am on version Nx 19.8.4 |
I have put in a Change Request that fixes this issues just waiting on review to be completed |
…TS rules to JSON files (#29457) This PR fixes an issue with React libs, where TS rules are being applied to JSON files. <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #28245 --------- Co-authored-by: Colum Ferry <cferry09@gmail.com> (cherry picked from commit cbbe14b)
…TS rules to JSON files (#29457) This PR fixes an issue with React libs, where TS rules are being applied to JSON files. <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #28245 --------- Co-authored-by: Colum Ferry <cferry09@gmail.com>
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
I encountered the following ESLint error when running the nx run-many -t lint command for a newly created workspace with plugin
Expected an assignment or function call and instead saw an expression. eslint@typescript-eslint/no-unused-expressions
Expected Behavior
The linting step should not fail with the @typescript-eslint/no-unused-expressions error
GitHub Repo
No response
Steps to Reproduce
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
Related to #28069
The text was updated successfully, but these errors were encountered: