rfcs
rfcs copied to clipboard
volta-cli
RFCs for changes to Volta
It's come up in some discussions that we might want to consider putting Notion config information in a separate config file (e.g. `my_project/.notionrc` or maybe `my_project/.config/notion/config`), and nudge projects towards...
Do we want some sort of low-level "escape hatch" primitive for letting projects install custom tools that don't install through dependencies. Use cases include things like gcc, Java, phantom, headless...
We should make sure to have enough hooks for teams to collect metrics on as much as possible.
We should store high-integrity checksums for provisioned artifacts. This means plugins need to be able to configure what kind of checksum is available and how to fetch them.
WIP, will flesh this out later: ## What? We should consider abiding by the [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html) This makes where notion lives on disk configurable, specifically it would abide...
Leaving some notes here, so I (or someone else with time) can circle back and write up a real RFC. `notion healthcheck` ## Goals * catch common issues * provide...
An important constraint: some Node packages use `which` to determine whether a particular tool is installed, so it's important for those tools to become invisible to the running Node process....
Should `notion` understand how to upgrade itself to new versions of `notion`? How does this interact with the various installers?
The development workflows are designed to make sure that the most ergonomic commands automatically set up the toolchain properly on demand. It should also be possible to use `notion` in...
What things should all installers do universally? - Create the appropriate directories - Find existing Node installs and gracefully supersede them with shims - Find existing global Node packages and...