This PR changes hyper-nano on Node to download the hyper-binary into the current working directory, which is to say wherever npx is ran from, typically the project directory. This is similar behavior to tools like the NextJS CLI when running next build.
With this, installing dependencies with yarn will not blow away the binary and any persisted data in the __hyper__ directory, as described in #537
This is breaking change, since users will need to add the hyper-nano binary and the __hyper__ directory to their .gitignore.
This PR also makes new versions of hyper-nano be published to our S3 bucket with a version suffix. This way, each hyper-nano version has a corresponding binary version to be downloaded from S3.
BREAKING CHANGE
closes #537
This PR changes
hyper-nanoon Node to download the hyper-binary into the current working directory, which is to say wherevernpxis ran from, typically the project directory. This is similar behavior to tools like the NextJS CLI when runningnext build.With this, installing dependencies with
yarnwill not blow away the binary and any persisted data in the__hyper__directory, as described in #537This is breaking change, since users will need to add the
hyper-nanobinary and the__hyper__directory to their.gitignore.This PR also makes new versions of
hyper-nanobe published to our S3 bucket with a version suffix. This way, eachhyper-nanoversion has a corresponding binary version to be downloaded from S3.