Publish as npm package

[quinn-dev]

While binaries don't require a functional Node.js setup and are easy to use (especially for not so tech-savy folks), npm packages can be installed globally and are easy to update.

Since this project primarily lives on GitHub at the moment and many people who find this repo likely already have node set up, a npm package would be a nice-to-have.

I'm not familiar with npm publishing so I don't know how much effort this would require.

[marcoklein]

I like that approach! Much more convenient than cloning the repository.

Only the loading of the config.json might cause trouble when you run the application from a global scope.

[therealshark]

You could use something like this package: https://github.com/sindresorhus/env-paths to find a good place for the config file