Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ADR to use asdf for node as well as golang #386

Merged
merged 15 commits into from
Jul 21, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Fix typo
  • Loading branch information
brandonlenz committed Jul 20, 2023
commit fe91b3731476acccc8902eb02b9c442ba2a92fed
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ ADR-0056 also lists the following as a disadvantage of using asdf for golang and
> installing node, yarn, or golang with asdf and another one of the similar tools can cause conflicts depending on which
> of the version manager tools is first in a particular path.

This is actually and advantage of using asdf, since one of the difficulties of managing asdf _and_ node is the obfuscation
This is actually an advantage of using asdf, since one of the difficulties of managing asdf _and_ node is the obfuscation
of which version will be shimmed by which tool. Picking and using _one_ tool is the solution. Since asdf is already required
for managing go, and it is capable of managing node, it is the logical choice.

Expand Down