add list command for testing flag combinations/piping to other scripts

[seansfkelley]

In large monorepos with many packages and their many names, it can be useful to test what your --scope, --ignore and --include-filtered-dependencies are about to do without having to run-oops-ctrl-c to get that feedback. You can also use it to feed to other scripts (with dependencies and in topologically-sorted order, both of which are quite handy)!

(This was a feature I added in Yerna that I found quite useful; I'm filing this issue for discussion purposes. Feel free to close if it's not a behavior you want in Lerna.)

[hzoo]

anything that gives more info like a dryrun type command sounds good to me

[hzoo]

offtopic: I know you mentioned you were frustrated at how things were going with Lerna earlier but I believe things are picking up again so would love to have your contributions (I'd like to work less on Lerna myself), thanks for the issue too!

[seansfkelley]

Yeah, "dry run" is also a good way to think about it.

I just finished filing a couple tickets with the features I found most valuable in Yerna that Lerna was lacking (it doubled as an experimenting ground for some features I really wanted). I have noticed the pace of development picking up! I'm happy to see that, but unfortunately I don't have the bandwidth to contribute more than these discussion tickets/reference implementations, which I do sincerely hope are useful!

[evocateur]

@seansfkelley This is the command in yerna you're talking about, correct?

[seansfkelley]

Yeah, exactly.

[mnasyrov]

It would be great to add an option to list absolute (or relative) paths of packages for using with external scripts/pipes.

[evocateur]

lerna ls gained a whole bunch of new options in v3, mimicking most of was npm ls provides. It also respects all the filtering options, including --since. Would that be sufficient to consider this issue closed?

[seansfkelley]

Looks like!

[lock]

This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs.