Recognize URIs starting with `dart-macro+`.

Such URIs belong to the same package as the
the rest of the URI would, but are not `package:` URIs,
and do not have a corresponding `package:` URI.
In this way, they behave like files inside the package,
but outside of `lib/`, even if they are `dart-macro+package:`
URIs.
7 files changed
tree: 2105b49f92341243b82c60c6d8f21e159f8aca36
  1. .github/
  2. example/
  3. lib/
  4. test/
  5. .gitignore
  6. analysis_options.yaml
  7. AUTHORS
  8. CHANGELOG.md
  9. CONTRIBUTING.md
  10. LICENSE
  11. pubspec.yaml
  12. README.md
README.md

Build Status pub package package publisher

Support for working with Package Configuration files as described in the Package Configuration v2 design document.

A Dart package configuration file is used to resolve Dart package names (e.g. foobar) to Dart files containing the source code for that package (e.g. file:///Users/myuser/.pub-cache/hosted/pub.dartlang.org/foobar-1.1.0). The standard package configuration file is .dart_tool/package_config.json, and is written by the Dart tool when the command dart pub get is run.

The primary libraries of this package are

  • package_config.dart: Defines the PackageConfig class and other types needed to use package configurations, and provides functions to find, read and write package configuration files.

  • package_config_types.dart: Just the PackageConfig class and other types needed to use package configurations. This library does not depend on dart:io.

The package includes deprecated backwards compatible functionality to work with the .packages file. This functionality will not be maintained, and will be removed in a future version of this package.