FVM

Fix Flutter version for your team with FVM

When we build Flutter projects in a team, using different Flutter versions can create hard bugs. So I use FVM (Flutter Version Management) to fix one Flutter version for the project.

My goals are simple:

• New teammates can set up quickly.

• The whole team uses the same Flutter version.

• We can upgrade or downgrade version when needed.

Install FVM

Official doc: Installation

Run:

dart pub global activate fvm

Check:

fvm --version

Fix Flutter version for the project

You can use one of these two ways.

Way 1: Use command

Official doc: Commands Reference

fvm use 3.27.4

Way 2: Set version in config file

Official doc: Configuration

Create or update:

.fvm/fvm_config.json

Content:

{
  "flutterSdkVersion": "3.27.4"
}

After this, the project will follow the exact version you set.

Add to .gitignore

Official doc: Configuration - Git Ignore

To avoid committing cache files, add:

# FVM
.fvm/flutter_sdk
.fvm/bin/cache
.fvm/versions
.fvm_cache/

Use FVM in daily Flutter commands

Official doc: Running Flutter

After setup, I always add fvm before Flutter commands:

fvm flutter pub get
fvm flutter analyze
fvm flutter test
fvm flutter run
fvm dart --version

This makes sure every command runs with the fixed Flutter version.

Setup flow for new teammates

When someone new joins the team, I share this short checklist:

1. dart pub global activate fvm

2. fvm use 3.27.4

3. fvm flutter pub get

4. fvm flutter run

With this flow, new teammates do not need to guess Flutter version.

Combine FVM with Make for shorter and safer commands

When the project grows, terminal commands become longer. So I combine FVM with Make to group many steps into one short command.

Step 1: Create a Makefile in project root

Example Makefile:

FVM := fvm
FVM_CACHE_PATH := $(CURDIR)/.fvm_cache
FVM_ENV := FVM_CACHE_PATH=$(FVM_CACHE_PATH) FLUTTER_SUPPRESS_ANALYTICS=true DART_SUPPRESS_ANALYTICS=true

.PHONY: init
init:
	$(FVM_ENV) $(FVM) install 3.27.4
	$(FVM_ENV) $(FVM) use 3.27.4 --force
	$(FVM_ENV) $(FVM) flutter pub get

Step 2: Run one command

make init

Without Make, most people need to type:

fvm install 3.27.4
fvm use 3.27.4 --force
fvm flutter pub get

Result: from 3 lines to 1 line, easier to remember, easier to teach new teammates, and less chance to miss a step.

If you want full details about grouping commands with Make, check this article:

Make

Update + FVM - Version management

Official doc: Commands Reference | Common Workflows | Release In Multiple Channels

When you need a new Flutter version, update with:

fvm use 3.29.0

Or edit .fvm/fvm_config.json, then run again:

fvm flutter pub get

Buy Me a Coffee | Support Me on Ko-fi