Yarn: Yarn list doesn't match NPM

[Timer]

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

[richardbowman]

Also, it doesn't seem to have a way to list the production-only dependencies of the project. No matter if prior to running yarn list you've only run yarn install -production or even more ideally it would work to run yarn list --production regardless of what was installed, like works with npm.

[monsterkodi]

I stumbled upon these differences as well.
I would also like yarn to copy the npm ls format.
It is prettier, more effective and more useful (IMHO;)
yarn list --depth=0 should just list the production (top level) packages. like npm ls does.
maybe have a yarn list --flat do the current bahaviour.

but i like the coloring, to be fair :-)

[alexilyaev]

Still an issue:

$ npm list postcss-reporter
react-es6-starter@0.0.0 /path/to/project
└─┬ stylelint@8.1.1
  └── postcss-reporter@5.0.0

$ yarn list postcss-reporter
yarn list v1.0.1
└─ postcss-reporter@5.0.0
✨  Done in 0.71s.

Tested on my repo:
https://github.com/alexilyaev/react-es6-starter

[pvdz]

I can repro this by creating a set of bogus nested packages. I see that the output depends on how you install it.

If you install the package through npm then npm will show you the tree while yarn does not.

When you install it through yarn then both engines show the same flat tree (and then npm displays warnings about packages being extraneous).

I can try to fix this but something tells me this is working as intended as a side effect of how yarn organizes packages.

Please discuss the best way to resolve this ticket.

[pvdz]

I put the example up here:
https://github.com/qfox/yarn/tree/list-yarn-vs-npm/__tests__/fixtures/list/match-npm

And actually, yarn list level5 doesn't even work unless you have installed the package with yarn. I think it reads the information from the yarn.lock file either way. It will bail the list command if that file doesn't exist.

[alexilyaev]

Even when you install with Yarn only, npm list shows a tree whereas yarn list shows a flat list (which is quite useless).

Example:
https://github.com/alexilyaev/react-es6-starter

$ yarn list wrappy
yarn list v1.2.1
warning Filtering by arguments is deprecated. Please use the pattern option instead.
└─ wrappy@1.0.2
✨  Done in 0.63s.

$ npm list wrappy
react-es6-starter@0.0.0 /Users/alex/www/Node/Personal/react-es6-starter
├─┬ eslint@4.8.0
│ └─┬ glob@7.1.2
│   ├─┬ inflight@1.0.6
│   │ └── wrappy@1.0.2
│   └─┬ once@1.4.0
│     └── wrappy@1.0.2  deduped
└─┬ webpack-dev-server@2.9.1
  └─┬ chokidar@1.7.0
    └─┬ fsevents@1.1.2
      └─┬ node-pre-gyp@0.6.36
        ├─┬ rimraf@2.6.1
        │ └─┬ glob@7.1.2
        │   └─┬ inflight@1.0.6
        │     └── wrappy@1.0.2  deduped
        └─┬ tar-pack@3.4.0
          └─┬ once@1.4.0
            └── wrappy@1.0.2

P.S.

What's up with the warning of using a filter?
Do I have to use yarn list --pattern wrappy now?

Why make life harder?!

[crhistianramirez]

Any workaround for finding that information besides manually tracking down dependencies :(

edit: I guess if you're desperate like me and have too many dependencies to do manually you can blow away yarn.lock and generate the the package-lock.json. I also had to delete my .npmrc file which was supressing the generation of the package-lock.json.

[monolithed]

I could't find the --pattern option. Why you show that warning? --cache-folder, --focus, --no-progress other are "very important" options, but the most popular without any manuals is just yarn list package.