These packages provide libraries for generating Dart code.
Defines the interfaces for creating a Builder which is a way of doing codegen
that is compatible across build systems (pub, bazel, standalone runner).
For packages doing code generation this should generally be the only package against which there is a public dependency. Packages may have a dev_depenency on one or more of the other packages.
In particular, transformers should only be exposed via a separate package, which
has a dependency on build_barback. This allows core packages to not leak the
dependency on barback and all of its transitive deps to all consumers.
Allows wrapping up a Builder as a Transformer so that it can be run in pub
or vice-versa.
Support for parsing build.yaml files. Used by build_runner.
Support for discovering the sub-modules within packages and creating summaries
of those modules. Used by build_web_compilers but should not be used directly
by most users.
An implementation of the Resolver interface to use the analyzer during build
steps.
Provides utilities to enact builds and a way to automatically run builds based on configuration.
This package should generally be a dev_dependency as it is used to run
standalone builds. The only exception would be wrapping the build and watch
methods with some other package.
Stub implementations for classes in Build and some utilities for running
instances of builds and checking their outputs.
This package generally only be a dev_dependency as it introduces a dependency on package:test. The exception to that would be if you were creating another testing-only package that wraps this one.
Provides the dart2js and dartdevc support for your package. To use this
package you should add it as a dev_dependency.
If you are using the automated build scripts, your project will automatically start being compiled with dartdevc, and you can start developing with chrome without any configuration.
The e2e_example
directory has demonstrations of running a Builder both
through pub (see the transformers section of pubspec.yaml) and in place (see
the tool/build.dart file). In real situations a project would choose one or
the other approach rather than mix both.