Closed yharaskrik closed 2 years ago
Hey! Can you provide a repo that produces this error so that I can investigate it further?
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. If we missed this issue please reply to keep it active. Thanks for being a part of the Nx community! 🙏
Hi, we are still having the issue in our 13.1.3 environment. We are currently struggeling with upgrading due to several other nx issues (mainly cache calculation). We hope we can get the upgrade through with 13.7.1 now and will re-check again. Please un-stale.
@NotSoImportant would you be able to provide a reproduction so that we can investigate this further?
Hi, as this happens in a private repo / server I will try my best to create a public repo and provide it here.
Thanks!
I had the same issue in my workspace, after a very long investigation I've noticed that eslint runs multiple times per each tsconfig file you have in your lib. Currently eslint doesn't support tsconfig references and Nx defines by default different tsconfig for lib and specs and when you define parserOptions.project with the wildcard then multiple compiler are created and if you have a wide codebase to scan in your tsconfig includes you end up is slow or not ending programs. If you want to solve the problem you can try using a single tsconfig file for lib and specs.
Thank you @daton89. Let me check if this is also the case here.
Thanks @daton89 for this hint. Problem is solved after removing the following config from every .eslintrc.json → "overrides" section
"parserOptions": {
"project": "./tsconfig.*?.json" // or different paths here
},
Glad you solved it @NotSoImportant
Indeed, that section should not exist in your .eslintrc.json
.
@yharaskrik did any of this help you? If not, please try to provide a minimal reproduction so we can investigate further.
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
Running
nx lint --fix
on a library either runs intoMaximum call stack
error (angular lib) orJavaScript heap out of memory
error (node lib)Angular lib has type aware checking enabled in the tsconfig Angular lib:
Node lib:
Also seems to not work without the
--fix
flagExpected Behavior
Should be able to lint and fix
Steps to Reproduce
Upgrade to v13 and run linting
This issue may not be prioritized if details are not provided to help us reproduce the issue.
Failure Logs
Environment
Tried with @typescript-eslint v4 (the version Nx installed) as well as v5, no dice.
Fully doesn't work with eslint v8