slipHQ/run-wasm

Packages have both a `package-lock.json` and a `yarn.lock` file

Dhaiwat10 opened this issue · 3 comments

Dhaiwat10 commented

Describe the bug
Packages have both a package-lock.json and a yarn.lock file. Intentional?

Dhaiwat10 commented

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?

jsjoeio commented

I think that is a result of this PR: #92

  • 👍2
cameronmoreau commented

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

  • 👍2