analyzer 0.30.0-alpha.1

  • Installing
  • Versions
  • 87

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 dartanalyzer and Dart Analysis Server can be configured with either an analysis_options.yaml or .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:


Post issues and feature requests at

Questions and discussions are welcome at the Dart Analyzer Discussion Group.


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.


  • Changed the API for creating BazelWorkspace. It should now be constructed using BazelWorkspace.find(). Note that this might return null in the event that the given path is not part of a BazelWorkspace.
  • Added an AST structure to support asserts in constructor initializers (AssertInitializer). AstVisitor classes must now implement visitAssertInitializer().
  • Changed the API for creating PartOfDirective. It now accepts a StringLiteral URI, to accomodate "part of" declarations with a URI string rather than a library name.
  • Removed AST constructors. AST nodes should now be created using astFactory, located in package:analyzer/dart/ast/standard_ast_factory.dart.


  • Removed Element.docRange.


  • Corresponds with the analyzer/server in the 1.20.0-dev.1.0 SDK.


  • Fixed PubSummaryManager linking when a listed package does not have the unlinked bundle.


  • Added support for running the dev compiler in the browser.


  • Support for references to operators in doc comments (#26929).


  • Support for trailing commas in parameter and argument lists (#26647).
  • Strong mode breaking change: can now infer generic type arguments from the constructor invocation arguments (#25220).


  • (Internal) Corresponds with the analyzer/server in the 1.18.0-dev.4.0 SDK.


  • Restore EmbedderUriResolver API.


  • Ignore processing performance improvements.
  • EmbedderUriResolver API updates.


  • Added support for 'analysis_options.yaml' files as an alternative to '.analysis_options' files.


  • Moved the public and private API's for the element model into their proper places.
  • Added back support for auto-processing of plugins.


  • Support for DEP 37 (Assert with optional message).
  • Lexical support for DEP 40 (Interface libraries). This does not include any semantic checking to ensure that the implementation libraries are compatible with the interface library.
  • Cleaned up the initialization of plugins. Clients are now required to initialize plugins, possibly using the utility method AnalysisEngine.processRequiredPlugins().
  • Removed the old task model and code that supported it. None of the removed code was intended to be public API, but might be in use anyway.
  • Removed previously deprecated API's (marked with the @deprecated annotation).


  • Options processing API updated to accept untyped options maps (#25126).


  • (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.

Use this package as a library

1. Depend on it

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

  analyzer: "^0.30.0-alpha.1"

2. Install it

You can install packages from the command line:

with pub:

$ pub get

Alternatively, your editor might support pub get. 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';
Version Uploaded Documentation Archive
0.32.1 May 30, 2018 Go to the documentation of analyzer 0.32.1 Download analyzer 0.32.1 archive
0.32.0 May 14, 2018 Go to the documentation of analyzer 0.32.0 Download analyzer 0.32.0 archive
0.31.1 Feb 9, 2018 Go to the documentation of analyzer 0.31.1 Download analyzer 0.31.1 archive
0.31.0+1 Feb 2, 2018 Go to the documentation of analyzer 0.31.0+1 Download analyzer 0.31.0+1 archive
0.30.0+4 Sep 21, 2017 Go to the documentation of analyzer 0.30.0+4 Download analyzer 0.30.0+4 archive
0.30.0+3 Sep 21, 2017 Go to the documentation of analyzer 0.30.0+3 Download analyzer 0.30.0+3 archive
0.30.0+2 May 21, 2017 Go to the documentation of analyzer 0.30.0+2 Download analyzer 0.30.0+2 archive
0.30.0+1 May 21, 2017 Go to the documentation of analyzer 0.30.0+1 Download analyzer 0.30.0+1 archive
0.30.0 May 3, 2017 Go to the documentation of analyzer 0.30.0 Download analyzer 0.30.0 archive
0.29.11 May 2, 2017 Go to the documentation of analyzer 0.29.11 Download analyzer 0.29.11 archive

All 203 versions...


We analyzed this package on Jun 18, 2018, and provided a score, details, and suggestions below. Analysis was completed with status tool failures using:

  • Dart: 2.0.0-dev.60.0
  • pana: 0.11.3


Describes how popular the package is relative to other packages. [more]
94 / 100
Code health derived from static analysis. [more]
100 / 100
Reflects how tidy and up-to-date the package is. [more]
49 / 100
Overall score:
Weighted score of the above. [more]
Learn more about scoring.


Detected platforms: unsure

Error(s) prevent platform classification:

Make sure dartanalyzer runs.


  • Make sure dartanalyzer runs.

    Running dartanalyzer . failed with the following output:

    Invalid argument(s): Provided content does not align with expectations.
    `STDERR exceeded 100000 lines.`
  • Fix platform conflicts.

    Error(s) prevent platform classification:

    Make sure dartanalyzer runs.

  • Package is getting outdated.

    The package was released 71 weeks ago.

  • Package is pre-release.

    Pre-release versions should be used with caution, their API may change in breaking ways.

  • The description is too short.

    Add more detail about the package, what it does and what is its target use case. Try to write at least 60 characters.

  • Fix analysis and formatting issues.

    Analysis or formatting checks reported 14 hints.

    Run dartfmt to format lib/dart/ast/ast_factory.dart.

    Run dartfmt to format lib/dart/element/element.dart.

    Similar analysis of the following files failed:

    • lib/src/codegen/html.dart (hint)
    • lib/src/dart/analysis/file_state.dart (hint)
    • lib/src/dart/element/element.dart (hint)
    • lib/src/dart/error/hint_codes.dart (hint)
    • lib/src/dart/resolver/inheritance_manager.dart (hint)
    • lib/src/dart/sdk/patch.dart (hint)
    • lib/src/generated/element_resolver.dart (hint)
    • lib/src/generated/incremental_resolution_validator.dart (hint)
    • lib/src/generated/testing/test_type_provider.dart (hint)
    • lib/src/generated/workspace.dart (hint)
    • lib/src/summary/format.dart (hint)
    • lib/src/task/inputs.dart (hint)
  • Package is pre-v1 release.

    While there is nothing inherently wrong with versions of 0.*.*, it usually means that the author is still experimenting with the general direction API.

  • Maintain an example.

    None of the files in your example/ directory matches a known example patterns. Common file name patterns include: main.dart, example.dart or you could also use analyzer.dart.

  • Use analysis_options.yaml.

    Rename old .analysis_options file to analysis_options.yaml.


Package Constraint Resolved Available
Direct dependencies
Dart SDK >=1.20.0 <2.0.0
args >=0.12.1 <0.14.0 0.13.7 1.4.3
charcode ^1.1.0 1.1.1
cli_util ^0.0.1 0.0.1+2 0.1.3
collection ^1.10.1 1.14.10
crypto >=1.1.1 <3.0.0 2.0.5
front_end 0.1.0-alpha.1 0.1.0-alpha.1 0.1.1
glob ^1.0.3 1.1.5
html >=0.12.0 <1.14.0 0.13.3+1
isolate >=0.2.2 <2.0.0 1.1.0 2.0.1
meta ^1.0.2 1.1.5
package_config >=0.1.5 <2.0.0 1.0.3
path >=0.9.0 <2.0.0 1.6.0 1.6.1
plugin ^0.2.0 0.2.0+2
watcher >=0.9.6 <0.10.0 0.9.7+8
yaml ^2.1.2 2.1.14
Transitive dependencies
async 2.0.7
convert 2.0.1
csslib 0.14.4
logging 0.11.3+1
source_span 1.4.0
string_scanner 1.0.2
typed_data 1.1.5
utf 0.9.0+4
when 0.2.0
which 0.1.3
Dev dependencies
test ^0.12.0
test_reflective_loader ^0.1.0
typed_mock >=0.0.4 <1.0.0