With this release, we've reorganized our commands, improved version detection, and Windows support.
Up until now, when proto would attempt to detect a version, it would use a version from the closest
.prototools file, or tool specific file (
.nvmrc, etc), which ever matched first.
For the most part, this works great, but what if you wanted
.prototools to take precedence over
other files, even if found in a higher parent directory? You unfortunately couldn't.
first-available(default) - Will use the first available version that is found. Either from
.prototoolsor a tool specific file.
prefer-prototools- Prefer a
.prototoolsversion, even if found in a parent directory. If none found, falls back to tool specific file.
detect-strategy = "prefer-prototools"
proto tool command group (breaking)
Our CLI surface area has been growing and we felt it was time to start grouping commands, starting
with the new
proto tool command. This command will contain "not used
very often" subcommands in relation to tools and their plugins, primarily for managing plugins, and
viewing tool information and inventory. As such, we've deprecated and moved the following top-level
proto tool add.
proto tool remove.
proto tool list-plugins.
proto tool list.
proto tool info command
Continuing with the changes above, we're also introducing a new command,
proto tool info, which displays detailed information about a
tool and its backing plugin. For example:
$ proto tool info node
node - Node.js
Globals directory: ~/.proto/tools/node/globals/bin
- ~/.proto/bin/node (primary)
- ~/.proto/shims/node (primary)
This command also supports JSON output via
View the official release for a full list of changes.
- Added support to plugins to ignore certain paths when detecting a version.
- Updated Windows to create 3 shim files for each tool:
.ps1(powershell), and no extension (bash).