commit | a2fca9e7350bfc7006f33885e4ba611bf0309235 | [log] [tgz] |
---|---|---|
author | Nate Bosch <nbosch@google.com> | Mon Feb 25 10:44:54 2019 -0800 |
committer | Nate Bosch <nbosch@google.com> | Mon Feb 25 10:44:54 2019 -0800 |
tree | fad74de16adfb695b6e7881176120f82b9da6fa0 | |
parent | f03ff4fe8892fe6592446a7c8d8e2f19ac4b137f [diff] |
Prepare to republish `1.0.6` with as `1.0.9` Fixes #23
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.