Skip to main content

The present and future of editors and IDEs for Dart

When we started the Dart project in 2011, we challenged ourselves to deliver a structured and lightweight language that can be supported with productive editors and tools. To bootstrap the tooling ecosystem for Dart, we built Dart Editor to explore how to make Dart developers productive with code completion, source navigation, and static analysis.

Today, there are more editing and IDE options for a Dart developer than ever before. Developers are using a range of command-line tools, text editors, and full IDEs that support Dart. In what comes as no surprise, we've found that developers have very strong affinities to their particular editors, and that one size does not fit all. We've also learned that many developers are outgrowing Dart Editor, as they require source control support, plugins, extended customizability, and more.

To that end, we've shifted our strategy from focusing on a single Java-based editor, to focusing on low-level tools, the Dart Analysis Server, and plugins for editors. We are retiring Dart Editor at the Dart 1.11 release. WebStorm is the preferred IDE experience for Dart, and the Eclipse plugin for Dart will continue to be supported.

WebStorm and IntelliJ are full-featured IDEs, and both ship with the Dart plugin. The Dart plugin uses the Dart Analysis Server for its errors, warnings, quick fixes, and more. JetBrains editors have a robust plugin ecosystem, strong support for numerous languages and libraries, and are very customizable. Learn more about the various WebStorm editions and licenses, or download a WebStorm trial.

The Dart plugin for Sublime has strong community support, and is great for developers looking for a lightweight text editing experience for Dart. It now displays real-time errors and warnings from the Dart Analysis Server. It also supports numerous build commands (for dart2js, pub, etc.), syntax highlighting, and more.

We built DartPad for developers that want a friction-free introduction to the Dart language and libraries. DartPad, also based on the Dart Analysis Server, is perfect for dabbling in Dart, sharing snippets, answering Dart questions on StackOverflow, and exploring Dart APIs.

Another option is the Eclipse plugin for Dart, which we continue to support. The Eclipse plugin, which currently shares most of its code with Dart Editor, is powered by the Dart Analysis Server.

Server-side Dart developers can use Observatory for profiling, debugging, insights, and more. Observatory isn't an editor or IDE, but its real-time VM stats and debugger are a great complement to your editor.

The tooling ecosystem for Dart has come a long way. Stay productive!

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).

A stronger Dart for everyone

We are constantly asking ourselves:
How do we make developers even more productive when writing Dart apps? We believe that a critical part of the answer to this question is to make strongmode – a sound static type system for Dart – the standard for all Dart developers.

Teams that use Dart to build apps like Soundtrap, AdWords, AdSense, and Greentea say they really enjoy using strong mode features, such as early error detection. In fact, teams that have switched completely to strong mode cite not only early error detection but also better code readability and maintainability as major benefits. We hear this both from small teams and Рeven more so Рfrom large teams with hundreds of developers writing and maintaining millions of lines of Dart code. As Björn Sperber from Soundtrap says,
Strong mode and the smooth integration with IntelliJ is a joy to use and a huge improvement. If you’ve tried out Flutter, you’ve already used strong mode checks from the Dart analyzer.

Given the benefits …

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 …