Files
yarn/__tests__
Jimmy Chan a2defdbece feat(cli): Generate an empty lockfile when there are no dependencies (#5843)
**Summary**

this reverts most of #3395 992b5c9086406b57416e1b0c3c77bea894fc97f0 which appears only necessary to work around #3329 (requesting the yarn version with -v triggered install). As noted in #5839, `yarn -v` and `yarn check` no longer have `install` as a side effect and IMO, the original behavior where an empty lock file is generated as part of install is the correct behavior.

Many tools currently sniff for a yarn.lock file to determine if yarn is being used. It seems more consistent with `yarn import` which generates a lockfile even if the existing node_modules is empty.

fixes #5839 

**Test plan**

`yarn run test` passes
`yarn run lint` passes
`yarn-local install`  saves an empty lockfile
`yarn-local import`  continues to save an empty lockfile
`yarn-local -v` will not trigger install and will not generate a lock file. correctly displays a version.
`yarn-local check` will not trigger install and will not generate a lock file
2018-05-23 14:54:20 +01:00
..
2018-05-23 11:16:38 +01:00
2018-05-23 11:16:38 +01:00
2018-02-28 18:54:00 +00:00
2018-05-17 10:42:50 -07:00
2018-05-17 10:42:50 -07:00
2017-08-17 14:17:34 +01:00