The flutter run variants
Danny Tuppeny edited this page Jun 5, 2018
·
6 revisions
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.
- Home of the Wiki
- Roadmap
- API Reference (stable)
- API Reference (main)
- Glossary
- Contributor Guide
- Chat on Discord
- Design documents
- Code of Conduct
- Issue triage reports (latest)
- Our Values
- Tree hygiene
- Issue hygiene and Triage
- Style guide for Flutter repo
- Project teams
- Contributor access
- What should I work on?
- Popular issues
- Running and writing tests
- Release process
- Flutter Framework Gardener Rotation
- Rolling Dart
- Manual Engine Roll with Breaking Commits
- Updating Material Design Fonts & Icons
- Postmortems and Retrospectives
- Hotfix Documentation Best Practices
- In case of emergency
- Landing Changes With Autosubmit
- Setting up the Framework development environment
- The Framework architecture
- API Docs code block generation
- Running examples
- Using the Dart analyzer
- The flutter run variants
- Test coverage for package:flutter
- Writing a golden-file test for package:flutter
- Managing template image assets
- Setting up the Engine development environment
- Compiling the engine
- Debugging the engine
- Using Sanitizers with the Flutter Engine
- Testing the engine
- The Engine architecture
- Flutter's modes
- Crashes
- more...
- Setting up the Packages development environment
- Plugins and Packages repository structure
- Contributing to Plugins and Packages
- Understanding Packages tests
- Plugin Tests
- Releasing a Plugin or Package
- more...