dart run build_runner build web -o build -r
This will build to the /web
directory.
dart run build_runner build web -o build
This will build to the /build/web
directory.
manifest.json
:default_icon
in manifest.json
to dart_dev.png
(Note: this is not strictly necessary, but will help you to distinguish your local version of the extension from the published version)web/manifest.json
. IMPORTANT: DO NOT COMMIT THE KEY.{ "name": "Dart Debug Extension", "key": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", ... }
/dwds/debug_extension/web
web/manifest.json
, pubspec.yaml
, and in the CHANGELOG
.pub run build_runner build web -o build -r
At this point, you should manually verify that everything is working by following the steps in Local Development.
debug_extension/web
directory (NOT debug_extension/build/web
).version_XX.XX.XX.zip
(eg, version_1.24.0.zip
) and add it to the go/dart-debug-extension-zips folderYou must be a Googler to do this. Ask for help if not.
If you don’t see dart-bat as an option, you will need someone on the Dart team to add you to the dart-bat Google group.
The first time you do this, you will be asked to pay a $5 registration fee. The registration fee can be expensed.
The Chrome Web Store Developer Dashboard does not support rollbacks. Instead you must re-publish an earlier version. This means that the extension will still have to go through the review process, which can take anywhere from a few hours (most common) to a few days.
You must be a Googler to do this. Ask for help if not.
manifest.json
edit the version number to be the next sequential version after the current “bad” version (eg, the bad version is 1.28.0
and you are rolling back to version 1.27.0
. Therefore you change 1.27.0
to 1.29.0
).