This way 'npm publish' works and the package correctly has the
resources in a '/package' directory inside the tarball.
Tested by publishing locally, indeed the README is now correctly
shown at https://www.npmjs.com/package/mastodon-bot/v/1.0.1-test-raboof-3
Will release 1.0.2 from master after merging
This means that we always have the right version, regardless of what's
in the global environment. Note that npm scripts (including `npm
start`) automatically prepend `./node_modules/.bin` to $PATH, which is
how this works.
See also http://module.party