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

Discussion - Linking vs Setting env PATH to set the desired version #182

Open
PaulThompson opened this issue Jun 19, 2023 · 0 comments
Open

Comments

@PaulThompson
Copy link

I notice that selecting the desired version works by using the filesystem to link the desired version into place.

This means that the effect of selecting a particular deno version is persistent and is shared by all shells/processes for that user (assuming the usual setup where a user has ~/.dvm/bin on the PATH).

A different method would be to manipulate the environment variable PATH of the current shell, so it would select the desired deno version only for one particular shell and later subprocesses. This is the method used by https://github.com/ghosind/dvm

Different trade-off depending on whether users would expect a dvm use to have a user-wide global persistent effect or whether the choice should be scoped to the current environment.

Use case for the latter could be when a user has different projects that need different deno versions and they run concurrently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant