[DAEMON-87] Generate yarn.lock in distribution tarball
| GitHub Issue | n/a |
|---|---|
| Type | New Feature |
| Priority | Medium |
| Status | Resolved |
| Resolution | Invalid |
| Resolution Date | 2017-08-27T05:28:12.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Tooling |
| Labels | n/a |
| Reporter | Chris Barber |
| Assignee | Chris Barber |
| Created | 2017-05-15T21:34:57.000+0000 |
| Updated | 2017-10-26T03:03:33.000+0000 |
Description
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 bundledDependencies.
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.
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.