yarnpkg/yarn

Yarn list doesn't match NPM

Open

#2,846 opened on Mar 6, 2017

View on GitHub
 (12 comments) (2 reactions) (0 assignees)JavaScript (41,514 stars) (2,731 forks)batch import
cat-compatibilityhelp wantedneeds-discussiontriaged

Description

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

What is the current behavior? Doesn't correctly show where a dep is coming from.

Joes-MacBook-Pro:react-scripts joe$ yarn list loader-utils
yarn list v0.21.3
├─ eslint-loader@1.6.3
│  └─ loader-utils@1.0.3
├─ extract-text-webpack-plugin@2.0.0
│  └─ loader-utils@1.0.3
└─ loader-utils@0.2.17

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

What is the expected behavior?

Joes-MacBook-Pro:react-scripts joe$ npm ls loader-utils
react-scripts@0.9.3 /Users/joe/Documents/Development/OSS/create-react-app/packages/react-scripts
├─┬ babel-loader@6.3.2
│ └── loader-utils@0.2.17 
├─┬ eslint-loader@1.6.3
│ └── loader-utils@1.0.3 
└─┬ extract-text-webpack-plugin@2.0.0
  └── loader-utils@1.0.3

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

Joes-MacBook-Pro:react-scripts joe$ node -v
v6.10.0
Joes-MacBook-Pro:react-scripts joe$ npm -v
3.10.10
Joes-MacBook-Pro:react-scripts joe$ yarn --version
0.21.3

Contributor guide

Tech stack
javascriptnodejs
Domain
cli
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
understanding of npm/yarn dependency trees
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue reports that `yarn list` output does not match `npm ls` in showing the correct dependency tree. Investigate the `list` command implementation in Yarn's source code (likely in `src/cli/commands/list.js`). Compare the logic for deduplication and tree display with npm's behavior. Check for any existing comments or linked PRs (none found). The fix would involve adjusting how Yarn resolves and displays nested dependencies, possibly by iterating over the dependency graph differently.
Yarn list doesn't match NPM · yarnpkg/yarn#2846 | Good First Issue