Replies: 2 comments
-
|
Am I misunderstanding or is this a description of Package Configurations? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Temporary workaround is to remove such dependencies manually: sed -i '/^ *"dependsOn":/s/"@acme\/xx-[^"]*",\? *//g' build/@acme/xx-app/full/app/turbo.json |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
In monorepo root I have task
generatethat lets each package specify dependencies in its ownturbo.json, because it works differently forapi(node+apollo) andapp(next.js) packages:Additionally, our
appgeneratetask depends onapigeneratetask, like specified inapp/turbo.json:app, theapp/turbo.jsonis not pruned correctly and still contains that dependency.Is there any option to remove the dependencies to monorepo packages that are not part of the pruned tree?
cc @chris-olszewski
Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions