How to debug Turborepo pipeline #959
-
|
I wanted to try Turborepo at a new company I just started working for. They have an existing monorepo based on yarn workspaces. When I execute The turbo-build.log looks OK to me, the built files are in the |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
In addition to |
Beta Was this translation helpful? Give feedback.
-
|
Hey there, I just ran into this very issue today, and I found the problem with |
Beta Was this translation helpful? Give feedback.
-
|
By removing the packages one by one I managed to figure it out. There was a circular dependency in the package.json between two of the packages. Once removed, turborepo could proceed to build all the packages. The last package in the output was not one of the packages with a circular dependency so I think the original question still stands. Is there a way I could have gotten to this conclusion sooner with some better way of debugging? |
Beta Was this translation helpful? Give feedback.
In addition to
--graph, you can also use the new--dryand--dry=jsonflags inturbov1.2+. See docs here: https://turborepo.org/docs/reference/command-line-reference#--dry----dry-run