analyzer_testing: improve error message when trying to use built-in mocks Work towards https://github.com/dart-lang/sdk/issues/61597 The analyzer_testing package's mock packages are "data" or "resource" files which are notoriously hard to find on disk. No dart tooling I know of can give me "the root directory of a package which is referenced in a Dart program via "package:". Konstantin notes that a program may be compiled ahead of time, and so the running VM itself does not know where source files originally came from. When users of the analyzer_testing package try to use `addFlutterPackageDep` in a test, which attempts to locate the Dart SDK's `pkg/` root directory, they get a StateError. This CL adds more information and context to that error. Change-Id: I3ae55cd580c8fa16ca86d66e6f7b655b8f9bcc42 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/452532 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Samuel Rawlins <srawlins@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.