Replies: 2 comments 3 replies
-
@cassepipe I think From
|
Beta Was this translation helpful? Give feedback.
3 replies
-
It's a shame this feature doesn't seem to work reliably. I have a basic test project with 3 packages, A depends on B, B depends on C. B is consistently being built before C. I'm evaluating my tools for a major rewrite of an application I build. I'm currently using Yarn workspaces with wsrun to handle the order of building. I was really hoping to have a few less addons in my pipeline. |
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
-
Say let's say I have a fullstack monorepo with a
front
,back
andshared
package.I need
shared
to build beforefront
andback
, so I need to enforce some kind of build order.Since both
front
andback
declareshared
as a dependency with theworkspace
protocol, couldn't there be a flag that would run a script respective of the dependency tree so that for example apnpm run build --ordered
from the workspace root would respect that build order ?Coming from the C world I am surprised there's no way to ensure a basic build order int the npm world
Beta Was this translation helpful? Give feedback.
All reactions