Changelog
All notable changes to flutter_compile. See the full CHANGELOG.md on GitHub.
0.12.0
FLUTTER_COMPILE_SDKenvironment variable — IDE terminals now use the project-pinned SDK instead of always falling back to the global default- Shell env file (
~/.flutter_compile_env) SDK block is now conditional: defers to IDE-provided SDK path when set, uses global default in regular terminals - VS Code extension sets
FLUTTER_COMPILE_SDK+applyAtShellIntegrationso project-pinned SDKs survive shell init - IntelliJ plugin sets
FLUTTER_COMPILE_SDKviaLocalTerminalCustomizerfor the same behavior - Auto-migration on extension/plugin activation — rewrites old env file SDK blocks with the new guarded template
migratecommand rewrites SDK blocks withFLUTTER_COMPILE_SDKguard for existing CLI users- SDK validation now checks for
bin/flutterinstead of.git/HEAD, so SDKs installed from release archives (no.git) work correctly - Whitespace-tolerant SDK path resolution — directories with trailing spaces are now matched via fallback scan
sdk global,sdk use, andsdk removeall trim version names and use resolved paths- VS Code & IntelliJ extensions v0.3.1
0.11.1
- Switch CI to GitHub-hosted runners (ubuntu-latest, windows-latest, macos-latest)
- Correct build matrix — replace duplicate macOS entry with Ubuntu for coverage uploads
- Upgrade
json_rpc_2to ^4.1.0 andlintsto ^6.1.0
0.11.0
- Engine now builds from within the Flutter contributor checkout (monorepo alignment with flutter/flutter)
install enginerequiresinstall flutterfirst — engine lives inside the Flutter checkout- Add
--forceflag toinstall engineandsync enginefor forcedgclient syncwith automatic retry build enginenow prepends depot_tools to PATH automatically (no manual PATH setup needed)install flutter --ide vscode|intellijflag — skip or auto-accept IDE-specific prompts when called from extensionsdoctornow probes known depot_tools locations for gclient beyond PATH- Idempotent git remote setup in
install flutter,install devtools, andinstall engine(safe to re-run) - gclient template updated for monorepo (
name: ".",{{flutter_url}}) - Engine upstream URLs changed from flutter/engine to flutter/flutter
- Better error messages and manual recovery instructions for gclient sync failures
- VS Code extension v0.3.0 — dual SDK backend (Native + FVM), SDK Manager toggle button, doctor install actions
- IntelliJ plugin v0.3.0 — mode dropdown for Native vs FVM backend, enhanced CLI integration
0.10.1
- RC config read/write now splits on first colon only, fixing Windows drive-letter paths
- File watcher path matching handles Windows backslash separators
- Add
TempHomeisolation tosdk execandsdk globaltests - Increase file watcher test timeouts for Windows CI reliability
0.10.0
- Add
daemoncommand — JSON-RPC 2.0 daemon for real-time IDE communication over stdin/stdout - Daemon supports
sdk.list,sdk.global.get/set,sdk.use.get/set,doctor,config.list/get/set,status,version,shutdownmethods - Daemon sends
sdk.changedandconfig.changednotifications on file system changes - Add
uicommand — interactive terminal UI dashboard for SDK management - TUI provides four tabs: SDKs, Environments, Builds, Doctor
- Extract reusable helpers:
gatherSdkList(),gatherDoctorChecks(),gatherStatus(),gatherConfig() - Add file watcher with 500ms debounce for
.flutter_compilercand.flutter-versionchanges - Add
--forceflag tosdk install - Add
isValidGitRepo()validation for partial/corrupted clones - Idempotent PATH management —
switch,uninstall, andsdk globaluse regex-based block detection - VS Code extension MVP — status bar SDK version, quick pick switcher, sidebar panels
- IntelliJ plugin MVP — toolbar combo box, tool window with SDK list and doctor output
0.9.0
- Add
synccommand to sync contributor environments with upstream - Add
fcpexecutable alias - Add
--jsonflag tosdk list,doctor,config list, andstatus - Add Windows support — cross-platform PATH management, shell config detection, host architecture resolution
- Platform-aware PATH export templates for PowerShell
doctorchecks for Visual Studio on Windows
0.8.0
- Add
sdk execcommand to run commands through the resolved SDK sdk installauto-sets global default when installing the first SDKsdk removeallows removing the global SDK and cleans up config
0.7.0
- Add
sdk globalcommand to set or show the global default - Add
sdk usecommand to pin SDK version per project (.flutter-version) - PUB_CACHE isolation — each installed SDK uses its own
.pub-cachedirectory sdk listnow annotates entries with(global)and(project)markerssdk removeguards against removing global default or project-pinned SDK
0.6.0
- Add
sdkcommand to install and manage multiple Flutter SDK versions - Add
dralias fordoctorandupalias forupdate - Replace all
exit()calls withFlutterCompileException - Centralized exception handling in command runner
0.5.1
- Upgrade mason_logger to ^0.3.3 and pub_updater to ^0.5.0
0.5.0
- Add
cleancommand to remove engine build output directories - Add
configcommand to view and modify.flutter_compilercfrom CLI uninstall flutternow removes PATH exports and cleans config
0.4.0
- Add
testcommand to run Flutter tests with a local engine build - Add
statuscommand to show engine configuration and available builds
0.3.1
- Add code coverage reporting and Codecov integration
0.3.0
- Add
runcommand to launch Flutter apps with a local engine build - Add
--gnand--no-gnflags tobuild enginefor incremental rebuilds
0.2.0
- Automate Flutter engine setup (
install engine) — depot_tools, gclient sync, git remotes - Add
build enginecommand with GN flag resolution and ninja builds - Support all platforms — android, ios, macos, linux, web, host
- Extend
doctorwith depot_tools, ninja, Xcode, and engine environment checks - Implement
uninstall enginewith optional depot_tools cleanup
0.1.0
- Add
doctorcommand for environment health checks - Implement
uninstall devtoolswith PATH and config cleanup
0.0.3
- Add support for compiling DevTools
0.0.2
- Fix broken links and tests
0.0.1
- Initial release