tag | 67eb0f8553c38452c62a39450ddda2397346ea73 | |
---|---|---|
tagger | Kevin Moore <kevmoo@google.com> | Fri Jul 20 14:42:03 2018 -0700 |
object | 3cbc7cd48214f43fdd251b0140da41c93173b589 |
commit | 3cbc7cd48214f43fdd251b0140da41c93173b589 | [log] [tgz] |
---|---|---|
author | Patrice Chalin <chalin@users.noreply.github.com> | Fri Jul 20 16:47:51 2018 -0400 |
committer | Kevin Moore <kevmoo@users.noreply.github.com> | Fri Jul 20 13:47:51 2018 -0700 |
tree | 459808946a2e849e57e099dbf50df09bf295d194 | |
parent | 286f1653bcb000ab5cb842252566afddf26102a0 [diff] |
chore: set max SDK version to <3.0.0 (#15)
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.