The static analyzer evaluates your Dart code, checking for errors and warnings that are specified in the Dart Language Specification.
Many tools in the Dart ecosystem (including IDEs, DartPad, and dartanalyzer) perform static analysis on code. Most of these tools (with the exception of DartPad) allow you to customize static analysis. The next section points you to where you can learn how to customize static analysis.
Customizing static analysis
You can customize the behavior of the analyzer or the linter
by adding an analysis options file (
the root of your package. The analysis options file allows
you to enable the lint rules appropriate to your project.
For example, adding the
close_sinks rule ensures that all
sink methods include a
close() call. For further information, see
Customize Static Analysis.
Adding static analysis to your tool
If you aren’t writing a Dart tool, you can ignore this section.
You have two options for adding static analysis to your Dart tool: the analysis server or package:analyzer.
If your tool requires continuous analysis or can handle exchanging text messages with a local server, use the analysis server. (See the Analysis Server API Specification for protocol details.) The following tools use the analysis server:
If your tool requires access to the abstract syntax tree (AST), use the package:analyzer library. The following tools use package:analyzer:
You might also be interested in the Dart analyzer discussion group.