Allows wrapping up a
Builder as a
Transformer so that it can be run in
Builder from Pub
Builder instance with
new BuilderTransformer(builder) and use it
like any other Transformer. The Builder used this way must follow the rules of
other Transformers, it cannot use inputs from outside the package where the
Transformer is specified in pubspec.yaml
Using an exisiting
Transformer instance with
new TransformerBuilder(transformer) and
run as any other
Builder. The Transformer instance used this way must follow
the rules of other Builders:
- It cannot overwrite files it uses as inputs.
- It must know before building what the outputs will be (it must be a
Features and bugs #
Please file feature requests and bugs at the issue tracker.
- Support the latest
- Update to
- Stop casting
srcimport from package:build.
- Internally uses
AnalysisOptionswith the following changes:
- Does not
- Does not
This makes the resolver implementation identical to the experience using the bazel_codegen, but it is technically a breaking change if you relied on the current behavior.
TransformerAssetReader#findAssetsnow returns a
Stream<AssetId>to match the latest
buildpackage, but this isn't considered a breaking change since the api is unsupported and throws in this implementation.
- Use a single
ResourceManagerfor all calls to
BuilderTransformer. This makes
Resources be shared across all build steps for a given package and Builder.
- Breaking: Resolver interface updated for breaking change in
BuilderTransformeris now an
AggregateTransformer. This should be transparent for most use cases but could have errors if an instance was assigned to a variable of type
BuilderTransformerno longer accepts a
Resolversinstance, instead it will create and manage Resolvers on its own.
- Update to build 0.9.0
TransformerBuildermust be constructed with a
buildExtensionconfiguration. Transformers wrapped as a builder must have outputs which vary only by input extension.
- Only use the global log from
- Upgrade to build 0.8.0
- Support the global log from
Updated to reflect the new support for reading/writing as bytes in the
package, and the removal of the
New Features #
BuilderTransformernow supports wrapping transformers that read or write their inputs as bytes.
- The Resolver implementation now has
isLibraryto check whether an Asset is a Library and throws an exception rather than returns null on
getLibrarywhen it isn't
Breaking Changes #
- Stopped exporting
lib/src/util/barback.dartwhich contains internal only utilities. Specifically, the following items are no longer public (some are deleted entirely or had breaking changes as well):
- Prevent asset writing from escaping beyond the
complete()call in BuildStepImpl
- Fix a bug forwarding logs from a
- Initial separate release - split off from
Use this package as a library
1. Depend on it
Add this to your package's pubspec.yaml file:
dependencies: build_barback: ^0.5.0+4
2. Install it
You can install packages from the command line:
$ pub get
Alternatively, your editor might support
Check the docs for your editor to learn more.
3. Import it
Now in your Dart code, you can use:
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
The package version is not analyzed, because it does not support Dart 2. Until this is resolved, the package will receive a health and maintenance score of 0.
Analysis issues and suggestions
Support Dart 2 in
The SDK constraint in
pubspec.yaml doesn't allow the Dart 2.0.0 release. For information about upgrading it to be Dart 2 compatible, please see https://dart.dev/dart-2#migration.
Maintenance issues and suggestions
dartdoc successfully runs on your package's source files. (-10 points)
Dependencies were not resolved.
|Dart SDK||>=2.0.0-dev.9 <2.0.0|