Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding --scope to ls or some way to determine which packages are depended upon for a single package #381

Closed
Steven-Evans opened this issue Oct 18, 2016 · 6 comments

Comments

@Steven-Evans
Copy link

Supposing a monorepo has multiple common dependent packages for services which are also in the same repository, it would be useful to know the complete list of packages that a particular service depends on. For example:

Service-1 depends on Auth
Auth depends on Common
Service-2 depends on Auth and Profile
Profile depends on Common

Then lerna ls --scope Service-1 outputs something like:
Service-1
Auth
Common

@Steven-Evans
Copy link
Author

Steven-Evans commented Oct 18, 2016

#382 PR with possible changes. Works for me but may be sloppy? Thoughts are appreciated on both code and whether this should even be considered part of master.

@lukebatchelor
Copy link
Contributor

Just linking this here for completeness re: the quiet flag #133

@ccrowhurstram
Copy link

Feature sounds very interesting... can you make sure it works with #365 when it lands (not sure if you need to anything, just a "heads up")

@Steven-Evans
Copy link
Author

Steven-Evans commented Oct 19, 2016

I gave it a quick glance and it seems like it shouldn't be a problem. packages and packageGraph are still defined during runPreparations.

As per my comment on the PR, I'm going to create a new PR to remove the --quiet flag since @thejameskyle suggested the intent to remove the lerna version line of output altogether, which is somewhat unrelated to this.

Edit: new PR #384

@jamiebuilds
Copy link
Contributor

Moving to #384

@lock
Copy link

lock bot commented Dec 28, 2018

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.

@lock lock bot locked as resolved and limited conversation to collaborators Dec 28, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants