FVM vs Vagrant

FVM manages Flutter SDK versions by project, allowing teams to keep builds consistent while using different versions across projects. A project’s `.fvmrc` file records its selected Flutter version and can include project-specific settings and flavors. FVM switches among installed SDKs without downloading them again. It can identify unreferenced versions, preview cleanup candidates, and remove unused SDKs with `fvm cleanup`. The documentation describes commands suitable for CI/CD automation and support for custom Flutter repositories. FVM provides packages for macOS, Linux, and Windows, with architecture availability varying by system. Installation options include a shell script, Homebrew, Chocolatey, Pub, and standalone packages. FVM detects VS Code and updates `.vscode/settings.json` for the Dart Code extension to use the project’s managed SDK. Android Studio and IntelliJ settings must be configured separately to point to the FVM SDK path. JSON API commands expose installed SDKs, releases, cleanup data, environment context, and project configuration. FVM stores known project roots in a machine-local file and says it does not scan disks for projects. The project is licensed under MIT.

Vagrant has no write-up on Specifiction yet; its figures are above.