Dave Herman
Dave Herman
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.
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...
What does a version specifier for a toolchain like Node or Yarn mean? For example, when someone asks for `8.5` does it mean `^8.5` in semver, or does it mean...
Need to include npx in the set of standard shims, and also flesh out the relationship between notion and npx.
Refactor cargo-cp-artifact to import the `copyArtifact` logic from [@neon-rs/artifact](https://www.npmjs.com/package/@neon-rs/artifact).