Closed Dhaiwat10 closed 2 years ago
Wait, no. It is not creating a new package-lock
file, it's already there. For some reason, yarn.lock
and package-lock
both are there. Is this intentional?
I think that is a result of this PR: https://github.com/slipHQ/run-wasm/pull/92
Good catch, out of the box Lerna used npm instead of yarn running bootstrap
I'll throw up a PR to use Yarn instead and remove the package-locks
Describe the bug Packages have both a package-lock.json and a yarn.lock file. Intentional?