[DAEMON-87] Generate yarn.lock in distribution tarball
When the distribution tarball is packaged, it consolidates all NPM dependencies into the top-level package.json and removes devDependencies from ALL appcd package.json files. All of the appcd-* packages are included in the tarball in the
node_modules directory and declared as
This ticket is to generate a
yarn.lock file for all non-appcd-* dependencies and their dependencies. There are many ways to do this, but the best for ease and performance is to simply merge the
yarn.lock files from every appcd-* directory.
- Chris Barber 2017-08-27
We have elected to publish each package to NPM and thus the distribution packaging is nothing more than doing a platform specific "npm install" and tarballing the result. We don't need to generate a yarn.lock file.