dart2js: The Dart-to-JavaScript Compiler

Use the dart2js tool to compile Dart code to deployable JavaScript. Another Dart-to-JavaScript compiler, dartdevc, is for development use only. The webdev build command uses dart2js by default. The webdev serve command uses dartdevc by default, but you can switch to dart2js using the --release flag.

The dart2js tool provides hints for improving your Dart code and removing unused code. Also see dartanalyzer, which performs a similar analysis but has a different implementation.

This page tells you how to use dart2js on the command line. It also give tips on debugging the JavaScript that dart2js generates.

Basic usage

Here’s an example of compiling a Dart file to JavaScript:

$ dart2js --out=test.js test.dart

This command produces a file that contains the JavaScript equivalent of your Dart code. It also produces a source map, which can help you debug the JavaScript version of the app more easily.

Build config usage

You can also configure dart2js options in a build config file. For more information, see the build_web_compilers README.


Basic options

Common command-line options for dart2js include:

-o <file> or --out=<file>
Generate the output into <file>. If not specified, the output goes in a file named out.js.
Enable assertion checking.
-m or --minify
Generate minified output.
-h or --help
Display help. (Use -vh for information about all options.)

Path and environment options

Some other handy options include:

Specify the path to the package resolution configuration file. For more information, see Package Resolution Configuration File. This option cannot be used with --package-root.
-p <path> or --package-root=<path>
Specify where to find “package:” imports. This option cannot be used with --packages.
Define an environment variable.
Display version information for dart2js.

Display options

The following options help you control the output of dart2js:

Don’t display warnings.
Don’t display hints.
Emit diagnostics, but don’t suggest how to get rid of the diagnosed problems.
-v or --verbose
Display lots of information.

Analysis options

The following options control the analysis that dart2js performs on Dart code:

Analyze even the code that isn’t reachable from main(). This option is useful for finding errors in libraries, but using it can result in bigger and slower output.
Analyze the code, but don’t generate code.
Like --analyze-only, but skip analysis of method bodies and field initializers.
Add colors to diagnostic messages.
Show warnings and hints generated from packages.
If true, disable dynamic generation of code in the generated output. This is necessary to satisfy CSP restrictions (see W3C Content Security Policy). The default is false.
Generate a file (with the suffix .info.json) that contains information about the generated code. You can inspect the generated file with the Dump Info Visualizer.

Size and speed options

When you’re ready to deploy, consider using the following options, in addition to minifying your app’s JavaScript. These options can improve the JavaScript that dart2js provides, but they have possible downsides.

For more information, see the --minify option (one of the dart2js basic options) and the Angular deployment guide.

Produce JavaScript that can be parsed more quickly by VMs. This option usually results in larger JavaScript files with faster startup.
Assume that operations on numbers, strings, and lists have valid inputs. This option allows the compiler to drop runtime checks for those operations. A well-typed program is not guaranteed to have valid inputs, because (for example) any int can be null. This option often improves both size and speed.

Use this option only if you have enough testing to ensure that those checks are not needed; otherwise the program will behave unexpectedly.

For example, with --trust-primitives and the code m1(num x, dynamic y) => x + y;, the compiler assumes that x is non-null and y is a number. If those aren’t true, then m1 might return NaN or '$x$y', instead of throwing an error.

As another example, with --trust-primitives and the code m2(int x, list y) => y[x];, the compiler assumes that x is within range. If x is negative or too large, m2 might return null instead of throwing an error.

Assume that all types are correct. If the analyzer reports no issues in your code, we recommend using this option when deploying your app. This option can significantly improve both size and speed.

Helping dart2js generate better code

You can do a couple of things to improve the code that dart2js generates:

  • Write your code in a way that makes type inference easier.
  • Once you’re ready to deploy your app, minify it and consider using the dart2js size and speed options to reduce code size or startup time.

Follow these practices to help dart2js do better type inference, so it can generate smaller and faster JavaScript code:

  • Don’t use Function.apply().
  • Don’t override noSuchMethod().
  • Avoid setting variables to null.
  • Be consistent with the types of arguments you pass into each function or method.


This section gives tips for debugging dart2js-produced code in Chrome, Firefox, and Safari. Debugging the JavaScript produced by dart2js is easiest in browsers such as Chrome that support source maps.

Whichever browser you use, you should enable pausing on at least uncaught exceptions, and perhaps on all exceptions. For frameworks such as dart:async that wrap user code in try-catch, we recommend pausing on all exceptions.


To debug in Chrome:

  1. Open the Developer Tools window, as described in the Chrome DevTools documentation.
  2. Turn on source maps, as described in the video SourceMaps in Chrome.
  3. Enable debugging, either on all exceptions or only on uncaught exceptions, as described in How to set breakpoints.
  4. Reload your app.

Internet Explorer

To debug in Internet Explorer:

  1. Update to the latest version of Internet Explorer. (Source-map support was added to IE in April 2014).
  2. Load Developer Tools (F12). For more information, see Using the F12 developer tools.
  3. Reload the app. The debugger tab shows source-mapped files.
  4. Exception behavior can be controlled through Ctrl+Shift+E; the default is Break on unhandled exceptions.


Firefox doesn’t yet support source maps (see bug #771597).

To debug in Firefox:

  1. Enable the Developer Toolbar, as described in Kevin Dangoor’s blog post, New Firefox Command Line Helps You Develop Faster”.

  2. Click Pause on exceptions, as shown in the following figure. Firefox Toolbar

  3. Reload your app.


To debug in Safari:

  1. Turn on the Develop menu, as described in the Safari Web Inspector Tutorial.
  2. Enable breaks, either on all exceptions or only on uncaught exceptions. See Add a JavaScript breakpoint under Safari Developer Help.
  3. Reload your app.