-
Describe the feature you'd like to requestWith lerna, we have This basically lets you list packages and information in a parseable manner and also provides filtering so that you can, for example, do the following:
This is useful for pipelines since sometimes you don't want to build and deploy everything unless it actually changed. I couldn't find an alternative with the available commands today, so I'm just doing it through a bash script but I suppose it's best to streamline it through turborepo just to make sure everything is coherent. Describe the solution you'd likeWhatever mimics lerna, for my use-case is fine. The important part is the filtering in my case since otherwise it just lists all available packages. Describe alternatives you've consideredN/A |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
|
#271 might be related |
Beta Was this translation helpful? Give feedback.
-
|
I want to add that "changed" is a little bit more complex than the diff between commits, because if A is a dependency of B and A changes, then B should be considered changed even though not a single bit of code is different in that package |
Beta Was this translation helpful? Give feedback.
-
|
I'd like to see this feature please 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
Seems like you can more or less accomplish this today with something along these lines: turbo build --dry=json '--filter=...[main]' | jq -r '.packages[]'Which outputs something like: To break it down:
|
Beta Was this translation helpful? Give feedback.
Seems like you can more or less accomplish this today with something along these lines:
Which outputs something like:
To break it down:
build --drydoes a dry run of thebuildpipeline, and the output will show even those packages without abuildscript (note that it doesn't have to bebuild, any pipeline could do)=jsonformats the dry run output as json...means include dependencies (e.g. if package B depends on A, but only A changed, include both B and A)[main]…