Missing feature, compare with npm ls once
. Should yarn why once
be the replacement for it? If so, the dependency graph that it shows seems wrong.
[cpojer: ~/Projects/yarn (master)]$ yarn why once
yarn why v0.14.0
[1/3] 🤔 Why do we have the module "once"...?
[2/3] 🚚 Initialising dependency graph...
[3/3] 🔍 Finding dependency...
info Reasons this module exists
- "node-gyp#glob" depends on it
- "jest#jest-cli#istanbul-api" depends on it
[cpojer: ~/Projects/yarn (master)]$ npm ls once
[email protected] /Users/cpojer/Projects/yarn
├─┬ [email protected]
│ └─┬ [email protected]
│ └── [email protected]
├─┬ [email protected]
│ └─┬ [email protected]
│ └─┬ [email protected]
│ └── [email protected]
└─┬ [email protected]
└─┬ [email protected]
└── [email protected]
We have yarn ls <package>
now 😃
@torifat awesome!!
For anyone who comes here in search of the ls
command, yarn list <package>
works on v1.9.4
(ls
doesn't work).
yarn ls <package>
not found
❯ yarn ls react
yarn run v1.19.1
error Command "ls" not found.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Most helpful comment
For anyone who comes here in search of the
ls
command,yarn list <package>
works onv1.9.4
(ls
doesn't work).