Remove useless dependencies.

[shibd]

Motivation

In #235, wrong introduction of verbose dependencies. It will cause the installation to fail using yarn install.

Modifications

• Remove verbose dependence.
• Remove node-pre-gyp-github, is also useless dependence. It is responsible for publishing NAPI to Release page. Refer Upload binaries napi to release. #245; We don't need to publish.
• Compile NAPI of macOS with yarn to verify that yarn is available.
• Update package.lock.json file.

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

Documentation

• doc-required
  (Your PR needs to update docs and you will update later)

• doc-not-needed
  (Please explain why)

• doc
  (Your PR contains doc changes)

• doc-complete
  (Docs have been already added)

[shibd]

@BewareMyPower@RobertIndie@tisonkun I add yarn.lock to make sure developers who compile with yarn using the same dependent version.

[BewareMyPower]

Not sure whether should we add two lock files for both npm and yarn. When I ran yarn install in my local env, there was a warning:

$ yarn install --no-scripts
yarn install v1.22.19
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.

After the yarn install command is done, the yarn.lock file changed a lot:

$ git diff yarn.lock | wc -l
7082

[shibd]

Not sure whether should we add two lock files for both npm and yarn. When I ran yarn install in my local env, there was a warning:

$ yarn install --no-scripts
yarn install v1.22.19
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.

After the yarn install command is done, the yarn.lock file changed a lot:

$ git diff yarn.lock | wc -l
7082

You are right. For developers, we should only use one way to manage dependencies. I remove yarn.lock.

BTW: For users, It can optionally use yarn or npm. So, currently, we are not uploading package.lock.json to the npm repository.

In this PR, we verified the installation method using yarn.

[shibd]

@tisonkun@RobertIndie@BewareMyPower PTAL.

[RobertIndie]

What's the motivation for removing package-lock.json?

[shibd]

What's the motivation for removing package-lock.json?

Not deleted. Only updated.