We gladly accept contributions via GitHub pull requests!
You must complete the Contributor License Agreement. You can do this online, and it only takes a minute. If you‘ve never submitted code before, you must add your (or your organization’s) name and contact info to the AUTHORS file.
git clone https://github.com/flutter/devtools
flutter pub upgrade
From a separate terminal, start running a flutter app to connect to DevTools:
git clone https://github.com/flutter/gallery.git (this is an existing application with many examples of Flutter widgets)
To run DevTools as a Flutter web app, follow these steps.
First, perform one-time setup:
flutter config --enable-web
Now you can run the app at any time with the flutter command.
From the packages/devtools_app directory:
flutter run -d chrome
To test release performance:
flutter run -d web-server --release --dart-define=FLUTTER_WEB_USE_SKIA=true
You can also use
-d headless-server, which will start a headless server that serves the HTML files for the DevTools Flutter app.
To develop with a workflow that exercises the DevTools server <==> DevTools client connection, change to the
packages/devtools directory, and run:
flutter pub get dart bin/devtools.dart --debug
flutter run -d web-server from the
flutter run development web server
You can then open a browser at the regular DevTools server URL (typically http://127.0.0.1:9100). When you make changes on disk, you can hit
r in your command-line to rebuild the app, and refresh in your browser to see the changes. Hit
q in the command line to terminate both the
flutter run instance and the devtools server instance.
You can also try running the app in the Flutter desktop embedder on linux or macos.
NOTE: The Linux desktop version only works with the master branch of Flutter (and sometimes this is true for MacOS as well). Syncing to a the master branch of Flutter may fail with a runner version error. If this occurs run
flutter create . from
devtools/packages/devtools_app, re-generates files in the linux and macos directories.
Depending on your OS, set up like this:
flutter config --enable-macos-desktop
flutter config --enable-linux-desktop
Now you can run with either of the following:
flutter run -d macos
flutter run -d linux
We also roll DevTools' code into a bazel build system, where we need to run only the non-flutter code from the app. To facilitate this, please keep code that imports package:flutter under a directory named ‘flutter’.
test/flutter are all acceptable locations to put new Flutter code.
When we are ready to turn down the
dart:html web version of the app, we will delete all code that isn't inside of or imported by the flutter code.
If you're using VS Code to work on DevTools you can run DevTools from the editor using the VS Code tasks without having to run in a terminal window:
This will serve the application in the background and launch Google Chrome. Subsequent launches will just re-launch the browser since the task remains running in the background and rebuilding as necessary.
Run and debug the local version of the server with a release build:
Run Server with Release Build config. Press F5. This will produce a release build of DevTools and then debug the server (
bin/devtools.dart) to serve it.
cd packages/devtools and run
If you need to make breaking changes to DevTools that require changes to the server (such that DevTools cannot run against the live Pub version of devtools_server) it's critical that the devtools_server is released first and the version numbers in
packages/devtools_app/pubspec.yaml are updated. Please make sure this is clear on any PRs you open.
Make sure your Flutter SDK matches the tip of trunk before running these tests.
cd packages/devtools_app flutter test -j1
-j1 tells Flutter to run tests with 1 concurrent test runner. If your test run does not include the directory
devtools_app/test/integration_tests, then you do not need to include this flag. For example, it is OK to do the following:
flutter test test/ui/
Some of the golden file tests will fail if Flutter changes the implementation or diagnostic properties of widgets used by the inspector tests. If this happens, make sure the golden file output still looks reasonable and execute the following command to update the golden files.
This will update the master or stable goldens depending on whether you're on the stable Flutter branch.
To update goldens for both channels do:
flutter channel master ./tool/update_goldens.sh flutter channel stable ./tool/update_goldens.sh
All content not authored by the Flutter team must go in the third_party directory. As an expedient to make the third_party code work well with our build scripts, code in third_party should be given a stub pubspec.yaml file so that you can reference the resources from the packages directory from