multiple package manager lockfiles in web3.js

[wentokay]

Problem

There's a yarn.lock and a package-lock.json in web3.js

Proposed Solution

Pick one package manager for the project and remove the lockfile that's associated with the other one

[jstarry]

Yeah, @steveluscher why do we need both?

[steveluscher]

Yeah! I noticed that. I'm not sure when the npm one snuck in, but it should begone.

[jstarry]

package-lock.json was always in there, I noticed you added the additional yarn.lock file. I prefer npm personally, any reason you use yarn?

[steveluscher]

npm has gotten a lot better, but I still carry damage from the days that made the creation of yarn necessary.

[steveluscher]

Oops. Our build cache still relies on package-lock.json so it wasn't as simple as deleting it. I'll have to revisit this in a hot moment after I revert the deletion.

[steveluscher]

2da8c8f

[github-actions]

Because there has been no activity on this issue for 7 days since it was closed, it has been automatically locked. Please open a new issue if it requires a follow up.