Releases: ehmicky/nve
Releases · ehmicky/nve
Release 3.2.1
Dependencies
- Remove
npm-run-path
andfilter-obj
as direct production dependencies
Release 3.2.0
Features
- Improve speed
Release 3.1.4
Dependencies
- Remove
path-key
as a direct production dependency
Release 3.1.3
Dependencies
Release 3.1.2
Internal
- Internal changes
Release 3.1.1
Bug fixes
- Make the
progress
option default tofalse
programmatically.
Release 3.1.0
Features
- It is now possible to omit the
command
. For examplenve 8
instead ofnve 8 npm test
. This can be used to cache the Node.js binary download without executing any command.
Release 3.0.0
Breaking changes
nve VERSION
must now be followed bynode
. For examplenve 8
should now benve 8 node
andnve 8 file.js
should benve 8 node file.js
.- The
NVE_PROGRESS
environment variable has been removed. The--no-progress
option should be used instead. - The programmatic usage has changed: please see the new API
Features
- Global binaries can now be executed such as
nve 8 npm test
. Keep in mind that the binary must be compatible with the chosen Node.js version. For examplenpm
is only compatible with Node>=6
. - Local binaries can be executed as well
- Add the
--shell
option to run a command inside a shell - Add the
--mirror
option to change the base URL to retrieve Node.js binaries - Add the
--help
and--version
CLI flags - Execa is now used under the hood which provides with additional features and options when run programmatically
Bug fixes
- If the script spawns child processes, those will now use the correct Node.js version
- Ensure
nve
does not exit untilstdout
andstderr
have been flushed
Release 2.2.3
Internal
- Internal changes
Release 2.2.2
Bugs
- Improve error messages