Add package-lock.json and yarn.lock

[TimDaub]

Scope

• burner-wallet and potentially other components like dapparatus currently do not include package-lock.json or yarn.lock
• These files are supposed to be committed however as they provide integrity when installing dependencies

Deliverables

• Add yarn.lock and package-lock.json in all components used by the burner-wallet.

Roles

bounty gardener: @TimDaub / 15%
bounty worker: name / 75%
bounty reviewer: name / 15%

[johannbarbie]

by pedro:
You shouldnt include both lock files
You should use one or the other
Otherwise you dont have integrity between people developing with yarn and npm
Unless you include a pre-push script to update both for consistency
And even then they wouldnt always result the same

[dmihal]

Agreed, in todays call we seemed to agree to use Yarn and yarn.lock.

[NetizenAbel]

The npm package-lock.json should never be committed; the yarn.lock is meant to be. If you use yarn; it's best to alter the package.json to include a requirement for it. Either both must go, or make the good call to hop on to Yarn all the way.