-
Notifications
You must be signed in to change notification settings - Fork 996
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
Clarify what' yarn ls' is showing #181
Comments
It's also not clear what |
This should be re-opened, it's still not clear what |
@markstos I'll provide a detail explanation of what is being displayed here later today. |
@markstos At a glance from the work a year ago, this seems to be correct. I implemented the depth relative to the existing tree output that @kittens had put together, and not something that mirrors npm. If there's a desire to mirror npm, perhaps, that conversation is better moved to an RFC. cc: @BYK @bestander |
@olingern It does seem like |
@markstos What does bold mean in the |
Reposting from yarnkpkg/yarn
yarn ls
has no clear documentation. I would like to add some but it I want to be clear what is going on.From the screenshot, it looks like zip-stream requires a versioning of lodash@~3.2.0 in grey, while the bolded [email protected] is the actual version of lodash that was installed.
But.. looking into the code, the grey/"dim" npm modules that don't have a bold equivalent (ex: compress-commons) means that they have been hoisted up to the main
node_modules/
folder. So anything that is bolded, is actually dependencies that yarn decided it couldn't hoist out to the main folder. Is this mostly correct? Is there something else that should be known in the documentation?The text was updated successfully, but these errors were encountered: