Fabio/aves_mio1
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
aves_mio1/.flutter/docs/tool/The-flutter-run-variants.md
FabioMich66 19a982ede6
Some checks are pending
Quality check / Flutter analysis (push) Waiting to run
Details
Quality check / CodeQL analysis (java-kotlin) (push) Waiting to run
Details
first commit
2026-03-05 15:51:30 +01:00

1.3 KiB
Raw Permalink Blame History

The flutter run variants

We aspire to reach a state where flutter run has the following modes:

  • flutter run: builds a debug version of the app and starts it in "hot reload" mode, then shows the console UI to manipulate the running instance.
  • flutter run --no-hot: builds a debug version of the app and starts it directly, then shows the console UI to manipulate the running instance.
  • flutter run --profile: builds a profile version of the app and starts it directly, then shows the console UI to manipulate the running instance.
  • flutter run --release: builds a release version of the app and starts it directly, then shows the console UI to manipulate the running instance.

Adding --machine in any of the situations above spawns a flutter daemon which:

  • changes the output to JSON so that it can be more easily consumed by IDEs, and
  • allows the use of JSON commands to interact with the running application (e.g. stopping the application).

All of the commands above launch a Flutter application and do not return until that Flutter application exits. Adding --no-resident in any of the situations causes the command to return immediately after the application has been launched rather than waiting until the application exits.