Consider removing yarn.lock

[cseas]

npm/documentation#810

tldr:

Committing package-lock.json to the source code version control means that the project maintainers and CI systems will use a specific version of dependencies that may or may not match those defined in package.json. Because package-lock.json cannot be added to NPM registry (by design; see NPM shrinkwrap), projects that depend on a project that uses package-lock.json will themselves use package.json to resolve project's dependencies, i.e. what works for project maintainers/ CI systems might not work when the project is used as a dependency.

[divyanshkul]

Can I work on this?
CC: @cseas

[cseas]

Waiting for the Blade team to analyse and consider the suggestion.

With lock file

• you get a reproducible development environment but your consumers will almost always get a different package tree than what Blade is developed on.

Without lock file

• development environment won't be reproducible 1:1 at all times but the package tree of Blade devs will be much closer to what consumers actually install.

The third option is to enforce the library's package tree by shipping a shrinkwrap file. But yarn doesn't support that.