Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(238)

Unified Diff: CHANGELOG.md

Issue 2910523002: update changelog to mention pub support for dartdevc (Closed)
Patch Set: code review updates Created 3 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: CHANGELOG.md
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 7b8a311652b5465c17645a4d3e494473a5258dd9..b9759dc02d4e9ed559335deb1b2c78ce1b7171a3 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -76,6 +76,51 @@ entirely to allow inference to fill in the type.
### Tool Changes
* Pub
+ * Added support for the Dart Development Compiler in `build` and `serve`.
+
+ Unlike dart2js, this new compiler is modular, which allows pub to do
+ incremental re-builds for `pub serve`, and potentially `pub build` in the
+ future.
+
+ In practice what that means is you can edit your Dart files, refresh in
+ Chrome (or other supported browsers), and see your edits almost
+ immediately. This is because pub is only recompiling your package, not all
+ packages that you depend on.
+
+ There is one caveat with the new compiler, which is that your package and
+ your dependencies must all be strong mode clean. If you are getting an
+ error compiling one of your dependencies, you will need to file bugs or
+ send pull requests to get them strong mode clean.
+
+ There are two ways of opting into the new compiler:
+
+ * Use the new `--web-compiler` flag, which supports `dartdevc`,
+ `dart2js` or `none` as options. This is the easiest way to try things
+ out without changing the default.
+
+ * Add config to your pubspec. There is a new `web` key which supports a
+ single key called `compiler`. This is a map from mode names to
+ compiler to use. For example, to default to dartdevc in debug mode you
+ can add the following to your pubspec:
+
+ ```yaml
+ web:
+ compiler:
+ debug: dartdevc
+ ```
+
+ You can also use the new compiler to run your tests in Chrome much more
+ quickly than you can with dart2js. In order to do that, run
+ `pub serve test --web-compiler=dartdevc`, and then run
+ `pub run test -p chrome --pub-serve=8080`.
+
+ * The `--no-dart2js` flag has been deprecated in favor of
+ `--web-compiler=none`.
+ * Added support for the UNLICENSE file when validating licenses on
+ `pub lish`.
+ * Better handling for network errors when fetching packages. These are no
+ longer unhandled errors and won't print a stack trace unless you are
+ running in verbose mode.
* `pub build` will use a failing exit code if there are errors in any
transformer.
* Allow publishing packages that depend on the Flutter SDK.
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698