dart-sdk/pkg/analyzer_cli
Devon Carew e2fe203adc [deps] roll package:lints to the latest
Change-Id: I582f956cd4b712203c2f6dd630b4e1384040446d
Tested: analysis clean (this is a lint only related change)
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/329400
Reviewed-by: Phil Quitslund <pquitslund@google.com>
Reviewed-by: Samuel Rawlins <srawlins@google.com>
Commit-Queue: Devon Carew <devoncarew@google.com>
2023-10-05 03:36:59 +00:00
..
bin Remove build mode from analyzer_cli. 2021-03-12 17:05:37 +00:00
lib Bump package:lints to the latest; address instances of new lints. 2023-09-25 21:15:15 +00:00
test Update old linter site links to dart.dev 2023-08-04 19:45:23 +00:00
tool [deps] roll package:lints to the latest 2023-10-05 03:36:59 +00:00
.gitignore
analysis_options.yaml Enable new linter rules in analyzer packages 2022-11-21 23:02:38 +00:00
LICENSE Update LICENSE 2021-04-07 10:28:38 +00:00
OWNERS [infra] Add OWNERS to the Dart SDK 2022-02-14 14:06:34 +00:00
pubspec.yaml Enable language 3.0 for analyzer_cli/. 2023-04-06 19:04:38 +00:00
README.md Tweak dartanalyzer readme now that the package is only intended for internal use 2022-07-20 16:03:48 +00:00

SDK development code analysis

dartanalyzer used to be the tool for statically analyzing dart code at the command line. However, this tool has been replaced with dart analyze for this purpose in current SDKs and will no longer be published on pub.

Do not depend on the command line interface or other semantics in this directory as it is now an internal tool for SDK development, used as the dart2analyzer "compiler" for tools/test.py in the SDK. It is configured as part of the test runner, here.

SDK development usage

For SDK development, run analysis from the test tool to validate analysis conclusions on language samples in the testing directory. From the root of the SDK:

tools/test.py --build --use-sdk -c dart2analyzer co19_2 language_2

This will build the Dart VM and compile dartanalyzer into a snapshot, then use that snapshot while analyzing those directories under testing/. Without --use-sdk, test.py will use the source code version of the analyzer instead of the compiled one, which can be useful for debugging.