feat(compute/build): support wasm-tools installed into $PATH #1183
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Fastly CLI has historically installed any required software (e.g.
wasm-tools) inside of a CLI-managed directory.Some users prefer to manage these software dependencies themselves (e.g.
brew install wasm-tools).This PR supports that workflow by first checking the
$PATHand using whatever is installed there.Otherwise, the CLI will use the software from its own managed directory, and it will continue to keep it updated.
Software used from the user's
$PATHis not updated or managed by the CLI.