Clone this repo:
  1. f451f4c Merge pull request #501 from JPaulsen/improve_performance_invariant_booleans by Brian Wilkerson · 17 hours ago master
  2. 0999a4b Improve performance: Invariant Booleans by Juan Pablo Paulsen · 19 hours ago
  3. 07eba42 Merge pull request #514 from JPaulsen/improve_performance_traverse_nodes by Brian Wilkerson · 2 days ago
  4. 932a7bb Improve performance: traverseNodesInDfs and literal_only_boolean_expressions by Juan Pablo Paulsen · 2 days ago
  5. 3568eae Merge pull request #507 from JPaulsen/fix_unnecessary_this by Alexei Eleusis Diaz Vera · 2 days ago

Linter for Dart

A Dart style linter.

Build Status Build status Coverage Status Pub


The linter is bundled with the Dart SDK; if you have an updated Dart SDK already, you're done!

Alternatively, if you want to contribute to the linter or examine the source, clone the linter repo like this:

$ git clone


The linter gives you feedback to help you catch potential errors and keep your code in line with the published Dart Style Guide. Currently enforcable lint rules (or “lints”) are catalogued here and can be configured via an analysis options file. The linter is run from within the dartanalyzer command-line tool shipped with the Dart SDK. Assuming you have lints configured in an .analysis_options file with these contents:

    - annotate_overrides
    - hash_and_equals
    - prefer_is_not_empty

you could lint your package like this:

$ dartanalyzer --options .analysis_options .

and see any violations of the annotate_overrides, hash_and_equals, and prefer_is_not_empty rules in the console. In practice you would probably configure quite a few more rules (the full list is here). For more on configuring analysis, see the analysis option file docs.


Feedback is, of course, greatly appreciated and contributions are welcome! Please read the contribution guidelines; mechanics of writing lints are covered here.

Features and bugs

Please file feature requests and bugs at the issue tracker.