Skip to main content

Dart Lands First Set of Library v2 Changes

The first big set of "Dart library v2" changes landed in the bleeding_edge branch today, which means it's time to investigate changes required to your code and pub packages. Further details about the changes, along with tips for updating, are forthcoming. For now, here's what you, our intrepid Dart developers, need to know.



The biggest changes are to async and collections

Everyone's first question: so, what's new? Until we publish a more comprehensive list of changes, here's a short, incomplete list to wet your whistle:

  • The new dart:async library now contains Future, Timer, and Streams.
  • The Future class changed quite a bit. For example, chain and transform are now simply then.
  • The new dart:collection library has more functionality beyond the basics found in dart:core.
  • The Iterator class changed, with new methods moveNext() and current. Many new operations, and some old ones, work with Iterable.
  • List gets two new named constructors: List.fixedLength(length, {fill}) and List.filled(len, fill).
  • Lots more...

The bleeding_edge docs are available for further exploration. To be clear, there are more changes than what is listed above. A more detailed post is on its way.

The M2 build is stable for 2-3 weeks

If you use the M2 build (essentially the latest Editor build, revision 0.2.9 or 0.2.10), you are insulated from these changes for now. We do not intend to push the library changes to the Editor builds for at least two weeks. This gives us enough time to update internal and external packages pushing out a new build.

Docs for M2 libraries are now available

You can now access API docs that match the shipping version of the SDK and Editor. The api.dartlang.org site now redirects to api.dartlang.org/docs/releases/latest/ which tracks the version of the SDK that ships in the editor's (mostly) weekly releases. The bleeding_edge docs are still available, if you want to see what's coming up.


Lock your pubspec.yaml file, or avoid updates, for 2-3 weeks

If you use pub to integrate third-party libraries, we advise you to do one of the following to minimize risk of a breaking change:

  • Avoid running pub update until after you get a new version of the stable Editor and SDK. This will probably be 2-3 weeks from now.
  • Manually lock the versions of your dependencies, by updating your pubspec.yaml and using specific version numbers instead of the any keyword.

The bleeding_edge branch is a moving target

The bleeding_edge branch, which is where all these library changes are getting merged, is going to take a few days to settle down. If you're experimenting with Dart's SVN repository or otherwise working with bleeding_edge, be warned. We're not quite done with the merge, and we have tests to fix.

Pub authors: Learn about the new changes

If you are the author of one or more pub packages, now is a great time to learn about these changes. Wait until our build bots turn green, and then you can download a bleeding_edge build to try it out. Meanwhile, you can view the bleeding_edge docs. Fear not, you can install the bleeding_edge version alongside your M2 build.

Thank you for your patience and feedback


We know these changes cause work for all of you, our developers. Our aim is to respond to feedback now, and make these changes as quickly as we can, so we can get to 1.0 and a more stable Dart. Thank you for your patience. We look forward to your feedback on the mailing list, and your bug reports and feature requests at dartbug.com.


(Image courtesy of http://www.flickr.com/photos/vblibrary/4419780791/)

Popular posts from this blog

Dart in 2016: The fastest growing programming language at Google, 2nd fastest growing in TIOBE Index

Dart was the fastest growing programming language at Google in 2016 with millions of lines of code written. It also made it to TIOBE Index Top 20 this month (see TIOBE's methodology).

It takes time to build something as ambitious as Dart and, in some ways, Dart is still in its infancy. But we're glad the hard work is starting to pay off.

Many thanks to our amazing community!

We're going to celebrate by ... releasing 1.22 next week (as per our usual 6 week release schedule).

The new Google AdSense user interface: built with AngularDart

AdSense is a free, simple way to earn money by placing ads on your website. The team just launched a completely new version of their app for publishers. Read all about it here. We asked Daniel White, the tech lead for the project, some questions because the new UI happens to be built with Dart and Angular2.


AdSense launched way back in 2003. How long is it since the last big redesign?
Last big redesign was called ‘AdSense 3’ and launched about 6 years ago. It was written in Google Web Toolkit (GWT) and the UI has evolved through several iterations - but this is the first ground-up redesign in 6 years. There are a number of long-standing UX issues that we’ve taken the opportunity to solve. A big shout-out to our UX team who’ve been 100% behind this project. We couldn’t have done it without them!

How many software engineers worked on the project?
Purely on the AdSense applications, we have a team of close to 100. Around 25% of them write Dart.

How many lines of code?
We have around 160K LO…

AngularDart 2.1 and new Components

AngularDart got its own dedicated team 5 months ago. Last month, we launched 2.0 final on the Dart Developer Summit. Today, we’re releasing the first minor release after that: 2.1.

Since the focus of AngularDart is Productivity, Performance, Stability, there are no major breaking changes (see the changelog) — but a lot of behind-the-scenes improvements. Your apps will get slightly smaller and faster (even relative to 2.0 which already made huge strides in size and performance since the compiled-from-TypeScript days).

Many features that AngularJS had to implement for JavaScript and TypeScript are not needed in Dart (because Dart already has those features out-of-the-box). So we’re removing them from AngularDart. Renderer is deprecated in favor of plain-old dart:html. NgPlural is going away — Dart programs can use the package:intl library.

New components

On the Dart Developer Summit, we launched AngularDart Components — the material design widgets Google is using in customer-facing apps …