Invalid package dependency graph: cyclic dependency detected #1752
-
|
I'm not sure if this is a bug or if I'm doing something conceptually wrong. I reckon the latter. However. I have a monorepo (turborepo) with a few apps and a few packages. Let's say two of my packages are named I guess this is intended but I don't understand how to achieve what I want. Isn't it common that two packages uses code from one another? Thanks in advance! C |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
I'm not sure I've seen this case before, although admittedly, I haven't worked with a LOT of monorepos. I would recommend restructuring your monorepo so you don't have a cyclical dependency! One way would be to create a |
Beta Was this translation helpful? Give feedback.
-
|
Absolutely wild that this has so many downvotes when it's the only correct answer. A cyclic dependency is by definition something like described in the initial question where A imports from B which imports from A which imports from B which... The only way to fix that is to break the cycle and move relevant parts to C... so that you end up with something like this:
|
Beta Was this translation helpful? Give feedback.
-
|
I agree, this one is almost one year old but the solution has not changed and shouldn't have. This is correct, and the way to structure your packages |
Beta Was this translation helpful? Give feedback.
I'm not sure I've seen this case before, although admittedly, I haven't worked with a LOT of monorepos. I would recommend restructuring your monorepo so you don't have a cyclical dependency! One way would be to create a
pkg-cthat has the pieces that you need for one of the packages.