-
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.0 - new project - Expected an assignment or function call and instead saw an expression #28069
Closed
1 of 4 tasks
Comments
jaysoo
added a commit
that referenced
this issue
Sep 25, 2024
… TS rules to JSON files (#28102) This PR fixes an issue with buildable/publishable Angular 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 #28069 --------- Co-authored-by: James Henry <james@henry.sc>
FrozenPandaz
pushed a commit
that referenced
this issue
Sep 26, 2024
… TS rules to JSON files (#28102) This PR fixes an issue with buildable/publishable Angular 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 #28069 --------- Co-authored-by: James Henry <james@henry.sc>
4 tasks
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current Behavior
Description
I encountered the following ESLint error when running the
nx run-many -t build,lint,test
command for a newly created workspace:Expected Behavior
The linting step should not fail with the
@typescript-eslint/no-unused-expressions
error.GitHub Repo
https://github.com/wizardnet972/nx-repo-problem
Steps to Reproduce
Output
After executing the above commands, the lint step fails with the following output:
Nx Report
Failure Logs
No response
Package Manager Version
npm
Operating System
Additional Information
The text was updated successfully, but these errors were encountered: