We ended up breaking stuff in v0.23.0 because of
changes to the libraries used, this allows us to
both:

- See if this ever happens again
- Prove we've actually fixed the problem

Instead of installing to a location relative to the `binary.js` file,
which leaves us open to problems due to how package managers may
choose to work, use a /binary folder at the same level as the `package.json`
instead.