commit | 962014d7c80b3fadb03975d7d804d3fd856cbde9 | [log] [tgz] |
---|---|---|
author | Kevin Moore <kevmoo@google.com> | Wed Jan 15 12:33:25 2020 -0800 |
committer | Kevin Moore <kevmoo@google.com> | Wed Jan 15 12:33:25 2020 -0800 |
tree | bea3e237b0e39b62e435ff49ab6d4e4a8b5a8ab6 | |
parent | 7f1a0f392af2254fde243fdccec0048f604c180d [diff] |
fix ignore placement
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.