Skip to content

Conversation

bhushan-shah-dev
Copy link

Added RFC for a new command yarn show, inspired by this issue.

@ljharb
Copy link

ljharb commented Aug 16, 2020

The spelling “show” conflicts conceptually with npm show; I’d suggest finding an unused name.

@bhushan-shah-dev
Copy link
Author

Good point.

How about yarn explicit?

@fivethreeo
Copy link

Explicit is a «keyboardful» yarn showdeps or yarn versions or yarn dependencies

@kesor
Copy link

kesor commented Jun 22, 2023

If someone is actually using yarn list --depth=0 and parses the output, and after that issue is fixed they would get a different output ... is it really a "breaking" change?

Is it really so essential to introduce yet another subcommand that does exactly what 99% of people intuition is already telling them that yarn list --depth=0 should be doing?

Introducing yet another command is bad UX. Good UX is when you do what the people feel intuitively should "just work".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants