Publish to npm

[djfarrelly]

Purpose

The binary executable is great, but using npm is an easier way to consume, upgrade and publish updates to this package. Package on npm

$ npm install -g @bufferapp/kubesecret
$ kubesecret -V
0.4.0

This also closes #3.

Background

The binary method felt the most usable when this package was written in golang and we didn't want to use npm as a delivery method. We used pkg before for other binaries (buffer-dev) because we wanted them to be more easily usable for non-developers, but since this is a developer tool, I think it's ok to assume everyone on the engineering team has node and npm installed 😄

Review

Hey @kiriappeee, I was thinking of making another addition to this CLI and thought of this idea. We could continue to build + distribute the binary, but this might be simpler for folks on the team to download the binary off of Github and move it into their PATH. What do you think?

[kiriappeee]

Tested. Looks great to me @djfarrelly . Thanks for getting this up 👍

[kiriappeee]

Quick aside, this isn't necessary for this PR. Might be good to specify minimum versions of node for this package.

[djfarrelly]

2 great ideas @kiriappeee!

• I just specified the min version at Node 10. This should work w/ Node 8.x w/ async/await support, but 8 is not in LTS anymore so 10 should be a good minimum 😁.
• Good catch on keeping the -V flag correct, I decided to take your idea and require the package.json file directly to ensure that the version is always in sync to remove developer error in the future!

@kiriappeee, do you have an npm username? I want to add you to our npm org so you can publish packages there 😄