No git hash in listing

[FireController1847]

Do you want to request a feature or report a bug?

A mix between both?

What is the current behavior? Considering all of the open issues discussing issue with git repositories, I can tell yarn doesn't support them very well. But, nonetheless I couldn't find anything discussing this.

When running npm list where you have a git dependency (ex. discordjs/discord.js), it will list the current hash next to the git dependency.

Here's an example of npm list discord.js vs yarn list discord.js

// NPM
`-- discord.js@12.0.0-dev  (github:hydrabolt/discord.js#717e7f094a0b30a88ec48b073373223861e87b12)

// YARN
yarn list v1.9.0-20180706.1017
└─ discord.js@12.0.0-dev

If the current behavior is a bug, please provide the steps to reproduce.

1. Install any git module. I tested with discordjs/discord.js via yarn install discordjs/discord.js & npm install discordjs/discord.js
2. List said module. For my tests npm list discord.js and yarn list discord.js were the two commands.

What is the expected behavior? I'd expect it to list the hash of what I currently have downloaded. This makes it very difficult to know what hash I am on on the indev version, which results in me needing to use npm to install the module just so I can get support.

Please mention your node.js, yarn and operating system version.

>node -v
v10.7.0

>npm -v
6.1.0

>yarn -v
1.9.0-20180706.1017

[rally25rs]

Marking as a feature-request:

List git commit hash in output of yarn list when a package is from a git repo.