Charles Pierce
Charles Pierce
From a discussion on Discord, along with the multiple questions we've had around using `engines` instead of the custom `volta` key in `package.json`: One possible way to improve interoperability and...
Related to #959 Related to #282 As noted in [this comment](https://github.com/volta-cli/volta/issues/959#issuecomment-831412266), `.node-version` is intended to specify a single, _exact_ version, which is exactly what Volta requires for it's own guarantees....
Info ----- * Implements the changes described in https://github.com/volta-cli/rfcs/pull/47 * As discussed in the RFC, while using a statically-linked TLS implementation reduces our need to build for the unique CentOS...
Symlinks in Windows come with a bunch of restrictions and edge-cases that make it hard for Volta to correctly determine the name of the tool that was called. A few...
With all of the groundwork taken care of, we can actually create automatic updates. This will involve: * Checking the latest version available from the public repository (https://volta.sh/latest-version) and comparing...
Closes #987 Info ----- * Node now ships with Corepack, which is an alternative way to manage your package manager using a similar shim method to Volta. * However, we...
Suggested in #569: A command, analogous to [`n ls-remote`](https://github.com/tj/n#miscellaneous) that will show which versions of a given tool are available in the remote repository. We can likely take a version...
The `volta install` command is a fairly common point of confusion for new users in two ways: 1. It's overloaded: `volta install` both fetches a new version _and_ changes the...
When running a shim, Volta will walk up the directory tree to find the closest available `package.json` file to use as the project, with one exception: When the immediate parent...
This was attempted by dependabot, but ran into issues with a change to the `Error` API. Bumping manually and resolving the `Error` issue.