Provides an in-memory
Resolvers implementation for use with
This implementation does a monolithic analysis from source, with fine grained invalidation, which works well when it can be shared across multiple build steps in the same process. It is not however suitable for use in more general build systems, which should build up their analysis context using analyzer summaries.
dart-ext:imports would cause the resolver to fail. These uris will now be ignored.
BuildAssetUriResolver.restoreAbsolutenever returns null.
AnalysisDriver. There are behavior changes which may be breaking. The
LibraryElementinstances returned by the resolver will now:
Sourceinstances with different URIs than before.
importedLibrariesgetter. You can instead use the
importsgetter to see all the imports.
newkeyword for a working release on Dart 1 VM.
firstWhere(orElse)for compatibility with the SDK dev.45
resetcall to indicate that a complete build is finished.
code_transformerswith a near-identical implementation.
Add this to your package's pubspec.yaml file:
dependencies: build_resolvers: ^1.0.3
You can install packages from the command line:
$ pub get
$ flutter packages get
Alternatively, your editor might support
pub get or
flutter packages get.
Check the docs for your editor to learn more.
Now in your Dart code, you can use:
|1.0.3||Feb 13, 2019|
|1.0.2||Feb 6, 2019|
|1.0.1||Feb 4, 2019|
|1.0.0||Jan 31, 2019|
|0.2.3||Jan 14, 2019|
|0.2.2+7||Dec 5, 2018|
|0.2.2+6||Oct 8, 2018|
|0.2.2+5||Sep 25, 2018|
|0.2.2+4||Sep 24, 2018|
|0.2.2+3||Aug 21, 2018|
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
We analyzed this package on Feb 14, 2019, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
Detected platforms: Flutter, other
The package description is too short. (-20 points)
Add more detail to the
description field of
pubspec.yaml. Use 60 to 180 characters to describe the package, what it does, and its target use case.
Maintain an example. (-10 points)
Create a short demo in the
example/ directory to show how to use this package.
Common filename patterns include
build_resolvers.dart. Packages with multiple examples should provide
For more information see the pub package layout conventions.
|Dart SDK||>=2.0.0 <3.0.0|