build 0.12.7+2

Published Jul 16, 2018 • Updated: 1.1.1

Flutter other

README.md
CHANGELOG.md
Installing
Versions
89

#

`build` #

Defines the basic pieces of how a build happens and how they interact.

`Builder` #

The business logic for code generation. Most consumers of the build package will create custom implementations of Builder.

`BuildStep` #

The way a Builder interacts with the outside world. Defines the unit of work and allows reading/writing files and resolving Dart source code.

`Resolver` class

An interface into the dart analyzer to allow resolution of code that needs static analysis and/or code generation.

Differences between the `build` package and `pub` + `barback`.

If you currently implement transformers with package:barback for use with Dart v1 pub build and pub serve, see Upgrading from barback.

Implementing your own Builders #

If you have written a barback Transformer in the past, then the Builder API should be familiar to you. The main difference is that Builders must always configure outputs based on input extensions.

The basic API looks like this:

abstract class Builder {
  /// You can only output files in `build` that are configured here. You are not
  /// required to output all of these files, but no other [Builder] is allowed
  /// to produce the same outputs.
  Map<String, List<String>> get buildExtensions;

  /// Similar to `Transformer.apply`. This is where you build and output files.
  Future build(BuildStep buildStep);
}

Here is an implementation of a Builder which just copies files to other files with the same name, but an additional extension:

/// A really simple [Builder], it just makes copies!
class CopyBuilder implements Builder {
  final String extension;

  CopyBuilder(this.extension);

  Future build(BuildStep buildStep) async {
    /// Each [buildStep] has a single input.
    var inputId = buildStep.inputId;

    /// Create a new target [AssetId] based on the old one.
    var copy = inputId.addExtension(extension);
    var contents = await buildStep.readAsString(inputId);

    /// Write out the new asset.
    ///
    /// There is no need to `await` here, the system handles waiting on these
    /// files as necessary before advancing to the next phase.
    buildStep.writeAsString(copy, contents);
  }

  /// Configure output extensions. All possible inputs match the empty input
  /// extension. For each input 1 output is created with `extension` appended to
  /// the path.
  Map<String, List<String>> get buildExtensions => {'': [extension]};
}

It should be noted that you should never touch the file system directly. Go through the buildStep#readAsString and buildStep#writeAsString methods in order to read and write assets. This is what enables the package to track all of your dependencies and do incremental rebuilds. It is also what enables your Builder to run on different environments.

Using the analyzer #

If you need to do analyzer resolution, you can use the BuildStep#resolver object. This makes sure that all Builders in the system share the same analysis context, which greatly speeds up the overall system when multiple Builders are doing resolution.

Here is an example of a Builder which uses the resolve method:

class ResolvingCopyBuilder implements Builder {
  Future build(BuildStep buildStep) async {
    // Get the [LibraryElement] for the primary input.
    var entryLib = await buildStep.inputLibrary;
    // Resolves all libraries reachable from the primary input.
    var resolver = buildStep.resolver;
    // Get a [LibraryElement] for another asset.
    var libFromAsset = await resolver.libraryFor(
        new AssetId.resolve('some_import.dart', from: buildStep.inputId));
    // Or get a [LibraryElement] by name.
    var libByName = await resolver.findLibraryByName('my.library');
  }

  /// Configure outputs as well....
}

Once you have gotten a LibraryElement using one of the methods on Resolver, you are now just using the regular analyzer package to explore your app.

The build package includes a Resource class, which can give you an instance of an expensive object that is guaranteed to be unique across builds, but may be re-used by multiple build steps within a single build (to the extent that the implementation allows). It also gives you a way of disposing of your resource at the end of its lifecycle.

The Resource<T> constructor takes a single required argument which is a factory function that returns a FutureOr<T>. There is also a named argument dispose which is called at the end of life for the resource, with the instance that should be disposed. This returns a FutureOr<dynamic>.

So a simple example Resource would look like this:

final resource = new Resource(
  () => createMyExpensiveResource(),
  dispose: (instance) async {
    await instance.doSomeCleanup();
  });

You can get an instance of the underlying resource by using the BuildStep#fetchResource method, whose type signature looks like Future<T> fetchResource<T>(Resource<T>).

Important Note: It may be tempting to try and use a Resource instance to cache information from previous build steps (or even assets), but this should be avoided because it can break the soundness of the build, and may introduce subtle bugs for incremental builds (remember the whole build doesn't run every time!). The build package relies on the BuildStep#canRead and BuildStep#readAs* methods to track build step dependencies, so sidestepping those can and will break the dependency tracking, resulting in inconsistent and stale assets.

Features and bugs #

Please file feature requests and bugs at the issue tracker.

0.12.7+2 #

Increased the upper bound for the sdk to <3.0.0.

0.12.7+1 #

AssetIds can no longer be constructed with paths that reach outside their package.

0.12.7 #

Added Resolvers.reset method.

0.12.6 #

Added List<String> get pathSegments to AssetId.
log will now always return a Logger instance.
Support package:analyzer 0.32.0.

0.12.5 #

Add exclude support to FileDeletingBuilder.

0.12.4 #

Add FileDeletingBuilder.
Add PostProcesBuilderFactory typedef.

0.12.3 #

Added an isRoot boolean to BuilderOptions, which allows builders to have different behavior for the root package, if desired.
Add PostProcessBuilder. This is only supported by build_runner.

0.12.2 #

Include stack trace in log for exceptions throw by builders.

0.12.1 #

Add BuilderOptions.empty and BuilderOptions.overrideWith.

0.12.0+2 #

Bug Fix Correctly handle encoding AssetIds as URIs when they contain characters which are not valid for a path segment.

0.12.0+1 #

Support the latest analyzer package.

0.12.0 #

Breaking Changes #

Added the Future<Digest> digest(AssetId id) method to the AssetReader interface. There is a default implementation which uses readAsBytes and md5.

0.11.2 #

Bug Fix: MultiplexingBuilder now filters inputs rather than calling every builder on any input that matched any builder.

0.11.1 #

Add BuilderOptions and BuilderFactory interfaces. Along with package:build_config this will offer a consistent way to describe and create the Builder instances exposed by a package.

0.11.0 #

Breaking: AssetReader.findAssets now returns a Stream<AssetId> instead of an Iterable<AssetId>. This also impacts BuildStep since that implements AssetReader.

0.10.2+1 #

Fix an issue where multiple ResourceManagers would share Resource instances if running at the same time.

0.10.2 #

Added the MultiPackageAssetReader interface which allows globbing within any package.
- This is not exposed to typical users, only build system implementations need it. The BuildStep class does not implement this interface.
The docs for AssetReader#findAssets have changed such that it globs within the current package instead of the root package (typically defined as buildStep.inputId.package).
- Before you could run builders only on the root package, but now that you can run them on any package the old functionality no longer makes sense.

0.10.1 #

Remove restrictions around the root package when Builders are running. It is the responsibility of the build system to ensure that builders are only run on inputs that will produce outputs that can be written.
Added the Resource class, and BuildStep#fetchResource method.

0.10.0+1 #

Bug Fix: Capture asynchronous errors during asset writing.

0.10.0 #

Breaking: Removed deprecated method BuildStep.hasInput - all uses should be going through BuildStep.canRead.
Breaking: Resolver has asynchronous APIs for resolution and is retrieved synchronously from the BuildStep.
Breaking: Replaced Resolver.getLibrary with libraryFor and getLibraryByName with findLibraryByName.
Change AssetReader.canRead to always return a Future.

0.9.3 #

Add support for resolving asset: URIs into AssetIds
Add uri property on AssetId

0.9.1 #

Skip Builders which would produce no outputs.

0.9.0 #

Deprecate BuildStep.hasInput in favor of BuildStep.canRead.
Rename AssetReader.hasInput as canRead. This is breaking for implementers of AssetReader and for any clients passing a BuildStep as an AssetReader
Make canRead return a FutureOr for more flexibility
Drop ManagedBuildStep class.
Drop BuildStep.logger. All logging should go through the top level log.
BuildStep.writeAs* methods now take a FutureOr for content. Builders which produce content asynchronously can now set up the write without waiting for it to resolve.
Breaking declareOutputs is replaced with buildExtensions. All Builder implementations must now have outputs that vary only based on the extensions of inputs, rather than based on any part of the AssetId.

0.8.0 #

Add AssetReader.findAssets to allow listing assets by glob.

0.7.3 #

Add BuildStep.inputLibrary as a convenience.
Fix a bug in AssetId.resolve to prepend lib/ when resolving packages.

0.7.2 #

Add an AssetId.resolve constructor to easily construct AssetIds from import uris.
Capture 'print' calls inside running builds and automatically turn them in to log.info. Depending on the environment a print can be hazardous so this makes all builders safe and consistent by default.

0.7.1+1 #

Use comment syntax for generic method - not everyone is on an SDK version that supports the real syntax.

0.7.1 #

Add a top-level log getter which is scoped to running builds and can be used anywhere within a build rather than passing around a logger. This replaces the BuildStep.logger field.
Deprecate BuildStep.logger - it is replaced by log
Deprecate ManagedBuildStep, all build runs should go through runBuilders.

0.7.0 #

A number of changes to the apis, primarily to support reading/writing as bytes, as this is going to inevitably be a required feature. This will hopefully be the last breaking change before the 1.0 release, but it is a fairly large one.

New Features #

The AssetWriter class now has a Future writeAsBytes(AssetId id, List<int> bytes) method.
The AssetReader class now has a Future<List<int>> readAsBytes(AssetId id) method.
You no longer need to call Resolver#release on any resolvers you get from a BuildStep (in fact, the Resolver interface no longer has this method).
There is now a BuildStep#resolver getter, which resolves the primary input, and returns a Future<Resolver>. This replaces the BuildStep#resolve method.
Resolver has a new isLibrary method to check whether an asset is a Dart library source file before trying to resolve it's LibraryElement

Breaking Changes #

The Asset class has been removed entirely.
The AssetWriter#writeAsString signature has changed to Future writeAsString(AssetId id, String contents, {Encoding encoding}).
The type of the AssetWriterSpy#assetsWritten getter has changed from an Iterable<Asset> to an Iterable<AssetId>.
BuildStep#input has been changed to BuildStep#inputId, and its type has changed from Asset to AssetId. This means you must now use BuildStep#readAsString or BuildStep#readAsBytes to read the primary input, instead of it already being read in for you.
Resolver no longer has a release method (they are released for you).
BuildStep#resolve no longer exists, and has been replaced with the BuildStep#resolver getter.
Resolver.getLibrary will now throw a NonLibraryAssetException instead of return null if it is asked to resolve an impossible library.

Note: The changes to AssetReader and AssetWriter also affect BuildStep and other classes that implement those interfaces.

0.6.3 #

Add hook for build_barback to write assets from a Future

0.6.2 #

Remove unused dependencies

0.6.1 #

BuildStep now implements AssetReader and AssetWriter so it's easier to share with other code paths using a more limited interface.

0.6.0 #

BREAKING Move some classes and methods out of this package. If you are using build, watch, or serve, along with PhaseGroup and related classes add a dependency on build_runner. If you are using BuilderTransformer or TansformerBuilder add a dependency on build_barback.
BREAKING Resolvers is now an abstract class. If you were using the constructor const Resolvers() as a default instance import build_barback and used const BarbackResolvers() instead.

0.5.0 #

BREAKING BuilderTransformer must be constructed with a single Builder. Use the MultiplexingBuilder to cover cases with a list of builders
When using a MultiplexingBuilder if multiple Builders have overlapping outputs the entire step will not run rather than running builders up to the point where there is an overlap

0.4.1+3 #

With the default logger, print exceptions with a terse stack trace.
Provide a better error when an inputSet package cannot be found.
Fix dev_dependencies so tests run.

0.4.1+2 #

Stop using removed argument useSharedSources when constructing Resolvers
Support code_transformers 0.5.x

0.4.1+1 #

Support analyzer 0.29.x

0.4.1 #

Support analyzer 0.28.x

0.4.0 #

BREAKING BuilderTransformer must be constructed with a List<Builder> rather than inherit and override.
Simplifies Resolver interface so it is possible to add implementations which are less complex than the one from code_transformers.
Adds a Resolvers class and support for overriding the concrete Resolver that is used by build steps.
Updates some test expectations to match the new behavior of analyzer.

0.3.0+6 #

Convert packages paths in the file watcher to their absolute paths. This fixes #109.

0.3.0+5 #

Fix duplicate logs issue when running as a BuilderTransformer.
Support crypto 2.0.0.

0.3.0+4 #

Add error and stack trace to log messages from the BuilderTransformer.

0.3.0+3 #

Fixed BuilderTransformer so that logs are passed on to the TransformLogger.

0.3.0+2 #

Enable serving files outside the server root by default (enables serving files from other packages).

0.3.0+1 #

Fix an AssetGraph bug where generated nodes might be created as non-generated nodes if they are attempted to be read from previous build steps.

0.3.0 #

BREAKING Renamed values of three enums to be lower-case: BuildType, BuildStatus, and PackageDependencyType.
Updated to crypto ^1.0.0.
Added option to resolve additional entry points in buildStep.resolve.
Added option to pass in a custom Resolvers instance.

0.2.1 #

Added the deleteFilesByDefault option to all top level methods. This will skip the prompt to delete files, and instead act as if you responded y.
- Also by default in a non-console environment the prompt no longer exists and it will instead just exit with an error.
Added support for multiple build scripts. Each script now has its own asset graph based on a hash of the script uri.
- You need to be careful here, as you can get in an infinite loop if two separate build scripts keep triggering updates for each other.
- There is no explicit link between multiple scripts, so they operate as if all changes from other scripts were user edits. This will usually just do the "right thing", but may result in undesired behavior in some circumstances.
Improved logging for non-posix consoles.

0.2.0 #

Updated the top level classes to take a PhaseGroup instead of a List<List<Phase>>.
Added logic to handle nested package directories.
Basic windows support added, although it may still be unstable.
Significantly increased the resolving speed by using the same sources cache.
Added a basic README.
Moved the .build folder to .dart_tool/build. Other packages in the future may also use this folder.

0.1.4 #

Added top level serve function.
- Just like watch, but it provides a server which blocks on any ongoing builds before responding to requests.
Minor bug fixes.

0.1.3 #

Builds are now fully incremental, even on startup.
- Builds will be invalidated if the build script or any of its dependencies are updated since there is no way of knowing how that would affect things.
Added lastModified to AssetReader (only matters if you implement it).

0.1.2 #

Exposed the top level watch function. This can be used to watch the file system and run incremental rebuilds on changes.
- Initial build is still non-incremental.

0.1.1 #

Exposed the top level build function. This can be used to run builds.
- For this release all builds are non-incremental, and delete all previous build outputs when they start up.
- Creates a .build directory which should be added to your .gitignore.
Added resolve method to BuildStep which can give you a Resolver for an AssetId.
- This is experimental and may get moved out to a separate package.
- Resolves the full dart sdk so this is slow, first call will take multiple seconds. Subsequent calls are much faster though.
- Will end up marking all transitive deps as dependencies, so your files may end up being recompiled often when not entirely necessary (once we have incremental builds).
Added listAssetIds to AssetReader (only matters if you implement it).
Added delete to AssetWriter (also only matters if you implement it).

0.1.0 #

Initial version

Use this package as a library

1. Depend on it

Add this to your package's pubspec.yaml file:


dependencies:
  build: ^0.12.7+2

2. Install it

You can install packages from the command line:

with pub:


$ pub get

with Flutter:


$ flutter packages get

Alternatively, your editor might support pub get or flutter packages get. Check the docs for your editor to learn more.

3. Import it

Now in your Dart code, you can use:


import 'package:build/build.dart';

Version	Uploaded	Documentation	Archive
1.1.1	Jan 31, 2019
1.1.0	Jan 14, 2019
1.0.2	Dec 5, 2018
1.0.1	Oct 8, 2018
1.0.0	Sep 25, 2018
0.12.8	Sep 24, 2018
0.12.7+3	Aug 1, 2018
0.12.7+2	Jul 16, 2018
0.12.7	Jun 21, 2018
0.12.6	May 14, 2018

All 57 versions...

Popularity: Describes how popular the package is relative to other packages. [more]	90
Health: Code health derived from static analysis. [more]	100
Maintenance: Reflects how tidy and up-to-date the package is. [more]	70
Overall: Weighted score of the above. [more]	89

Learn more about scoring.

We analyzed this package on Feb 14, 2019, and provided a score, details, and suggestions below. Analysis was completed with status completed using:

Dart: 2.1.0
pana: 0.12.13

Platforms

Detected platforms: Flutter, other

Primary library: package:build/build.dart with components: io, isolate, build.

Maintenance suggestions

The package description is too short. (-20 points)

Add more detail to the description field of pubspec.yaml. Use 60 to 180 characters to describe the package, what it does, and its target use case.

Maintain an example. (-10 points)

Create a short demo in the example/ directory to show how to use this package.

Common filename patterns include main.dart, example.dart, and build.dart. Packages with multiple examples should provide example/README.md.

For more information see the pub package layout conventions.

Dependencies

Package	Constraint	Resolved	Available
Direct dependencies
Dart SDK	>=2.0.0-dev.9 <3.0.0
analyzer	>=0.27.1 <0.33.0	0.32.6	0.35.1
async	>=1.13.3 <3.0.0	2.0.8
crypto	>=0.9.2 <3.0.0	2.0.6
glob	^1.1.0	1.1.7
logging	^0.11.2	0.11.3+2
meta	^1.1.0	1.1.7
path	^1.1.0	1.6.2
Transitive dependencies
args		1.5.1
charcode		1.1.2
collection		1.14.11
convert		2.1.1
csslib		0.14.6
front_end		0.1.4+2	0.1.11
html		0.13.3+3
kernel		0.3.4+2	0.3.11
package_config		1.0.5
plugin		0.2.0+3
source_span		1.5.4
string_scanner		1.0.4
term_glyph		1.1.0
typed_data		1.1.6
utf		0.9.0+5
watcher		0.9.7+10
yaml		2.1.15
Dev dependencies
build_resolvers	^0.2.1
build_test	^0.10.0
test	^1.2.0

build 0.12.7+2

#

build #

Builder #

BuildStep #

Resolver class

Differences between the build package and pub + barback.

Implementing your own Builders #

Using the analyzer #

Sharing expensive objects across build steps #

Features and bugs #

0.12.7+2 #

0.12.7+1 #

0.12.7 #

0.12.6 #

0.12.5 #

0.12.4 #

0.12.3 #

0.12.2 #

0.12.1 #

0.12.0+2 #

0.12.0+1 #

0.12.0 #

Breaking Changes #

0.11.2 #

0.11.1 #

0.11.0 #

0.10.2+1 #

0.10.2 #

0.10.1 #

0.10.0+1 #

0.10.0 #

0.9.3 #

0.9.1 #

0.9.0 #

0.8.0 #

0.7.3 #

0.7.2 #

0.7.1+1 #

0.7.1 #

0.7.0 #

New Features #

Breaking Changes #

0.6.3 #

0.6.2 #

0.6.1 #

0.6.0 #

0.5.0 #

0.4.1+3 #

0.4.1+2 #

0.4.1+1 #

0.4.1 #

0.4.0 #

0.3.0+6 #

0.3.0+5 #

0.3.0+4 #

0.3.0+3 #

0.3.0+2 #

0.3.0+1 #

0.3.0 #

0.2.1 #

0.2.0 #

0.1.4 #

0.1.3 #

0.1.2 #

0.1.1 #

0.1.0 #

Use this package as a library

1. Depend on it

2. Install it

3. Import it

Platforms

Maintenance suggestions

Dependencies

`build` #

`Builder` #

`BuildStep` #

`Resolver` class

Differences between the `build` package and `pub` + `barback`.