rfcs
rfcs copied to clipboard
RFCs for changes to Volta
Proposal for updating `volta pin` to add a `--default` flag that replaces the need for `volta install`, combining all of the pin operations into a single `volta pin` command. [Rendered](https://github.com/charlespierce/rfcs/blob/volta_use/text/0000-volta-use.md)
> Roadmap of the necessary changes to support Yarn Berry (Yarn 2.0+) [Rendered](https://github.com/charlespierce/rfcs/blob/yarn_berry/text/0000-yarn-berry-support.md)
> Add first-class support for the pnpm package manager. [Rendered RFC](https://github.com/mikrostew/rfcs/blob/pnpm-support/text/0000-pnpm-support.md)
> Proposal to switch to a statically-linked TLS implementation for HTTPS downloads via the [`Rustls`](https://github.com/rustls/rustls) crate. [Rendered](https://github.com/charlespierce/rfcs/blob/static_link_tls/text/0000-static-link-tls.md)
Alternative to #50 Discussed on Discord here: https://discord.com/channels/413753499835301908/413753499835301917/982039620701270046 ## Proposed Behavior When volta needs to discover package.json configuration to choose a node version, it should: a) ascend the filesystem to...
Currently, monorepos rely on an `extends` property in each sub-project. This was done for a few reasons: - to avoid needing to crawl up the file tree to an undetermined...
Starting this as an issue, since there are a number of questions and I'm not sure of a full approach at the moment. # Motivation We have a number of...
From offline discussions: A large majority of the time when a user runs `volta install` while in a package, what they actually meant to do was `volta pin`. Additionally, it's...
Currently, we have a single global cache for all of the tools. However, some corporate environments have a limited subset of versions available (e.g. only specific versions of Node are...
My original design was that shims for third-party binaries would always resolve to a local dependency if it's present (similar to how `npx` and other tools work). My intuition was...