| commit | c61d7cfeed4d61b21924e5998c73c9a3c605a3e9 | [log] [tgz] |
|---|---|---|
| author | Nate Bosch <[email protected]> | Mon Feb 25 19:25:41 2019 |
| committer | GitHub <[email protected]> | Mon Feb 25 19:25:41 2019 |
| tree | e65f8d5682065377e224b7d2a23b3a047e088492 | |
| parent | cd2b4a3ddedd391be153ebe764d197bab46ab2a9 [diff] | |
| parent | d34ba6ec9b8f1a735e15841feacab8c723305374 [diff] |
Prepare to republish as 1.0.10 - Bump minimum SDK constraint to one that includes `Future` in `dart:core`. - Remove all `dart:async` imports which are no longer required. - Merge in branch that published as 1.0.9 to include changelog
A package that defines a common class, PackageResolver, for defining how to resolve package: URIs. This class may be based on the current isolate's package resolution strategy, but it may also be explicitly defined by the user—for example, you could create a resolver that represents the strategy used to compile a .dart.js file.
The Dart VM provides two mutually exclusive means of resolving package: URIs: a package spec and a package root.
A package spec usually comes in the form of a .packages file on the filesystem. It defines an individual root URL for each package name, so that package:$name/$path resolves to $root/$path.
A package root is a single URL that acts as the base for all package: URIs, so that package:$name/$path resolves to $base/$name/$path.
This normalizes access to these resolution schemes, and makes it easy for code to resolve package URIs no matter where the resolution information comes from.