analyzer 0.26.3

Analyzer for Dart

This package provides a low-level library that performs static analysis of Dart code. It is useful for tool integration and embedding.

End-users should use the dartanalyzer command-line tool to analyze their Dart code.

Integrators that want to add Dart support to their editor should use the Dart Analysis Server. The Analysis Server API Specification is available. If you are adding Dart support to an editor or IDE, please let us know by emailing our list.

Configuring the analyzer

Both the dartanalyzer and Dart Analysis Server can be configured with a .analysis_options file. This YAML file can control which files and paths are analyzed, which lints are applied, and more.

If you are embedding the analyzer library in your project, you are responsible for finding the .analysis_options file, parsing it, and configuring the analyzer.

The .analysis_options file should live at the root of your project (for example, next to your pubspec.yaml). Different embedders of analyzer, such as dartanalyzer or Dart Analysis Server, may choose to find the file in various different ways. Consult their documentation to learn more.

Here is an example file that instructs the analyzer to ignore two files:

    - test/_data/p4/lib/lib1.dart
    - test/_data/p5/p5.dart
    - test/_data/bad*.dart
    - test/_brokendata/**

Note that you can use globs, as defined by the glob package.

Here is an example file that enables the analyzer's strong mode:

  strong-mode: true

Here is an example file that enables two lint rules:

    - camel_case_types
    - empty_constructor_bodies

Check out all the available Dart lint rules.

You can combine the analyzer section and the linter section into a single configuration. Here is an example:

    - test/_data/p4/lib/lib1.dart
    - camel_case_types

Who uses this library?

Many tools embed this library, such as:

  • dartfmt - a formatter for Dart code
  • dartdoc - a documentation generator for Dart code
  • Dart Analysis Server - a stateful server that supports IDEs and editors


Questions and requests for additional functionality are welcome. Please open an issue at or by email


The APIs in this package are, quite frankly, a mess at the moment. They were originally machine generated by a translator and were based on an earlier Java implementation. Several of the API's still look like their Java predecessors (or worse) rather than clean Dart API's.

In addition, there is currently no clean distinction between public and internal APIs. We plan to address this issue but doing so will, unfortunately, require a large number of breaking changes. We will try to minimize the pain this causes for our clients, but some pain is inevitable.


See the LICENSE file.


  • (Internal) Support for _embedder.yaml discovery and processing.


  • Add code generation utilities for use in both analyzer and analysis server.


  • (Internal) Introduced context configuration logic (configureContext() extracted from server).


  • (Internal) Options validation plugin API update.


  • (Internal) Provisional options validation plugin API.


  • (Internal) Plugin processing fixes.


  • Fixes to address lint registry memory leaking.


  • New AnalysisContext API for associating configuration data with contexts (setConfigurationData() and getConfigurationData()).


  • OptionsProcessor extension point API changed to pass associated AnalysisContext instance into the optionsProcessed call-back.


  • Provisional (internal) plugin manifest parsing.


  • Plugin configuration ErrorHandler typedef API fix.


  • Provisional (internal) support for plugin configuration via .analysis_options.


  • Extension point for WorkManagerFactory(s).
  • Resolve enum documentation comments.
  • Fix display of parameter lists in servers Element structure (issue 24194)
  • Band-aid fix for issue #24191.


  • Removed a warning about importing unnamed libraries
  • Fix handling of empty URIs in .packages files (issue 24126)


  • Fix line starts in multiline comments (issue 23919).
  • Various small fixes to Windows path handling.
  • Update LineInfo computation during incremental resolution.
  • Make exclude list apply to contexts (issue 23941).
  • Fix type propagation for asynchronous for-in statements.
  • Fix ToStringVisitor for external functions (issue 23968).
  • Fix sorting of compilation unit members.
  • Add forwarding for DefaultFormalParameter metadata.
  • Fix most implementations of UriResolver.restoreAbsolute.
  • Disable dart2js hints by default.
  • Support older SDKs (Dart 1.11).


  • Add hook for listening to implicitly analyzed files
  • Add a PathFilter and AnalysisOptionsProvider utility classes to aid clients in excluding files from analysis when directed to do so by an options file.

  • API change: UriResolver.resolveUri(..) now takes an optional actualUri.
  • Change ResolutionCopier.visitAwaitExpression to copy *Type fields.
  • Fix highlight range for missing enum constant in switch (issue 23904).
  • Fix analyzer's treatment of ClassName?.staticMember to match spec.
  • Implement DEP 34 (less restricted mixins).
  • Fix some implementations of UriResolver.resolveUri(..) that did not properly handle the new actualUri argument.


  • Requires Dart SDK 1.12-dev or greater
  • Enable null-aware operators (DEP 9) by default.
  • Generic method support in the element model.


  • dart:sdk extension .sdkext changed to _sdkext (to play nicer with pub).


  • Initial support for analyzing dart:sdk extensions from .sdkext.


  • (Internal) code reorganization to address analysis warnings due to SDK reorg.
  • First steps towards .packages support.


  • Commandline interface moved to dedicated analyzer_cli package. Files moved:
  • bin/analyzer.dart
  • lib/options.dart
  • lib/src/analyzer_impl.dart
  • lib/src/error_formatter.dart
  • Removed dependency on the args package.


  • Changes in the async/await support.


New API:

  • Source.uri added.

Breaking changes:

  • DartSdk.fromEncoding replaced with fromFileUri.
  • Source.resolveRelative replaced with resolveRelativeUri.

1. Depend on it

Add this to your package's pubspec.yaml file:

  analyzer: "^0.26.3"

2. Install it

You can install packages from the command line:

$ pub get

Alternatively, your editor might support pub. Check the docs for your editor to learn more.

3. Import it

Now in your Dart code, you can use:

import 'package:analyzer/analyzer.dart';


Static analyzer for Dart.


Email Dart Team