Publish package-lock.json to npmjs.com

[ianhe8x]

Even though the project is organized in mono repo way via yarn workspace, we don't recommend user install the package to their global using yarn global add. It was detailed in #355.

The problem is we only have yarn.lock in the code base without package-lock.json. npm -g install doesn't recognize yarn.lock so when user tries to install our app, there are actually no lockfile used. It caused a lot dependency issues.

I can think of one solution, that we still use yarn and yarn.lock in the code base, but convert yarn.lock to package-lock.json via tools like synp when publishing packages to npmjs.com.

[jiqiang90]

imsnif/synp#74

Could successful convert yarn.lock v1, but v2:

Jis-MacBook-Pro:subql jiatwork$ synp --source-file yarn.lock --with-workspace
Unknown token: { line: 3, col: 2, type: 'INVALID', value: undefined } 3:2 in lockfile

[stwiname]

NPM doesn't allow publishing package-lock.json. We don't have any complaints as this being an issue, im going to close