nodenv v1.3.0 Release Notes
Release Date: 2019-05-04 // almost 5 years ago-
nodenv-version learns to describe aliases
๐จ When printing the current node version and its origin (how it was set),
nodenv-version now resolves any symlinks to determine the final
targeted version.๐จ It prints the version name as selected, an arrow and the aliased version
name, and finally the origin.
If the version is not an alias, the output is the same as before.This only affects the output of
nodenv version
;
nodenv-version-name
andnodenv-version-origin
are unaffected.โ Remove test-only abort messages
These messages are only printed if NODENV_NATIVE_EXT is set; and it is
โ only set for test runs. (It is not expected to be set by users.) Thus
these messages are only useful when running on travis, and I'd rather
โ there not be test-only code running for users.Ignore errors if nodenv-prefix fails
๐จ nodenv-prefix will print errors to STDERR if node isn't available in
๐ PATH. (As demonstrated on Travis, since the nvm's nodes are removed from
โ PATH by the test-helper.)We don't actually care if node is available in PATH or not for this
๐จ check, we only care to print the selected node and follow it if it's a
symlink. So if nodenv-prefix fails, the path would be empty, thus no
๐จ need to follow it and we just print the same message as before.๐จ Print versions in semantic order
๐ Take sort_versions function from node-build (which is broken).
๐ Use extended regular expression for simplicity
๐ Ignore semver-spec characters from sorting. (remove , ~, etc)
Ensure shorter version names sort first (.0 instead of .z)
Ensure node versions sort above others; iojs, chakra, etc (prefix a. if
leading digit)๐ Fix incorrect count of versions in
nodenv versions