-
Notifications
You must be signed in to change notification settings - Fork 809
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pkg: add lockfile #642
pkg: add lockfile #642
Conversation
This comment has been minimized.
This comment has been minimized.
62df14b
to
72dd4ef
Compare
72dd4ef
to
a916bfa
Compare
✅ Installed clean at a916bfa everything works and all test pass! Is there anything else a user can do to verify? Or |
You can change the hashes to something obviously wrong to verify that
Next is to verify that the hash is of the code that it's expected to be. |
``` bash | ||
$ npm install -g bcoin --production | ||
``` | ||
Bcoin is meant to be installed via git for security purposes, as there are security issues when installing via npm. All tagged commits for release should be signed by @chjj's [PGP key][keybase] (`B4B1F62DBAC084E333F3A04A8962AB9DE6666BBD`). Signed copies of node.js are available from [nodejs.org][node], or from your respective OS's package repositories. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Looks good. I love how small our package-lock.json is now. Going forward we should start doing tarball releases as well. I've been working simple tool which creates a non-npm tarball and generates a build file for the native dependencies. |
Closes #619