Replies: 5 comments
-
I started having this problem after upgrading to nx from 16.10 to 17.1.3 |
Beta Was this translation helpful? Give feedback.
-
I started getting this error after upgrading to v17 as well (only in CI pipelines). The solution was to switch from executing the |
Beta Was this translation helpful? Give feedback.
-
Same issue here when working with vscode. No warnings were showing anymore in the code and I had that same error in the eslint output. It started working again after making a change to nx.json and then reverted it ¯\_(ツ)_/¯ A colleague has the same issue but making changes to nx.json didn't make it work, so I have no clues why it started working again for me |
Beta Was this translation helpful? Give feedback.
-
It's all been a bit of a mess moving to v17, to be honest. So many issues. OK, we get some new ways of doing things... fine if they work, just a PITA if they don't. And they don't. Regretting ever "upgrading" from v16 at all. |
Beta Was this translation helpful? Give feedback.
-
I had the same issue, and created a bug report: #20752 |
Beta Was this translation helpful? Give feedback.
-
Hi!
I'm trying to introduce the eslint plugin rule
@nx/enforce-module-boundaries
to our monorepo to enforce module boundaries in our existing monorepo, but I'm getting this crash when runningyarn lint
.This is the first time we're importing anything nx related into our app so I'm wondering if I'm missing some extra configuration. Looking at the source code, it seems like its trying to
readCachedProjectGraph()
beforecreateProjectGraphAsync()
is called. Any thoughts would be appreciated. Thanks in advance!The changes are fairly minimal:
Beta Was this translation helpful? Give feedback.
All reactions