dvm global <version>
dvm global
Sets global in ~/.dvm/config.json. This is rule 3: what applies in a directory that has no
.dvmrc above it.
dvm global 3.13.2
With no argument it reports the current value:
dvm global
The global default is 3.13.2.
/Users/you/.dvm/config.json
The fallback for directories that pin nothing#
This is the difference between dvm and a version manager you have to remember to switch. The global default gives scratch directories, one-off scripts and your home directory a Dart, while a project with a
.dvmrc uses its own.
Leave it unset and directories with no pin fall through to rule 4: whatever
dart was already on your PATH. That is a perfectly reasonable way to run dvm.
No global default is set. Directories with no .dvmrc fall through to the first dart on PATH.
Set one with: dvm global <version>
It installs first#
Naming a version you do not have installs it, exactly as dvm use
does.
A global default that needs installing#
The global default is 3.9.0.
It is not installed. Run: dvm install 3.9.0
Exit code 1. This is the state dvm remove --force can leave behind, and it is worth fixing straight away: the global default applies to every command run outside a pinned project.
The same thing, two spellings#
dvm global 3.13.2
dvm use 3.13.2 --global
are identical. dvm use --global is there so use covers the concept too, whichever command you reached for first.
See also#
- Resolution Order — where rule 3 sits.
-
dvm which— confirm whether the global is what is actually applying.