Core functionality of the build_runner package. Exposes the imperative apis
for running pure Dart builds for
resetprior to build.
buildmethod now requires a list of
overrideGeneratedDirectorymethod which overrides the directory for generated outputs.
NoSuchMethodErrorthat the user could get when adding new dependencies.
pub run build_runner cleanto fix.
BuildConfigChangedException. These should be handled by scripts as described in the documentation.
package:buildversion constraint to
BuildOptionsstatic factory now takes a
LogSubscriptioninstead of a
BuildEnvironment. Logging should be start as early as possible to catch logs emitted during setup.
timingpackage for performance tracking.
BuildStep.trackStageto track performance of custom build stages within your builder.
packagessymlink within the
newkeyword for a working release on Dart 1 VM.
BuildEnvironmentmust now implement the
finalizeBuildmethod. There is a default implementation if you extend
BuildEnvironmentthat is a no-op.
IOEnvironmenthas moved to a named argument since
nullis an accepted value.
BuildOptionshas moved to the
IOEnvironmentconstructor, that causes the merged output directories to contain only symlinks, which is much faster than copying files.
FinalizedAssetViewclass which provides a list of all available assets to the
BuildEnvironmentduring the build finalization phase.
outputMaphas moved from
BuildOptionsto this constructor, as a named argument.
OverridableEnvironmentnow supports overriding the new
.dart_tool/buildis now based on a relative path to the build script instead of the absolute path.
.dart_tool/builddirectories to be reused across different computers and directories for the same project.
BuildPerformanceclass is now serializable, it has a
fromJsonconstructor and a
BuildOptions.logPerformanceDir, performance logs will be continuously written to that directory if provided.
build.yamlof the root package.
BuildPhasePerformance.actionhas been replaced with
BuilderActionPerformance.builderhas been replaced with
BuildResultno longer has an
failOnSeverearguments. Severe logs are always considered failing.
Initial release, migrating the core functionality of package:build_runner to this package.
Add this to your package's pubspec.yaml file:
dependencies: build_runner_core: ^2.0.3
You can install packages from the command line:
$ pub get
Alternatively, your editor might support
Check the docs for your editor to learn more.
Now in your Dart code, you can use:
|2.0.3||Feb 13, 2019|
|2.0.2||Jan 31, 2019|
|2.0.1||Jan 25, 2019|
|2.0.0||Jan 23, 2019|
|1.1.3||Jan 14, 2019|
|1.1.2||Dec 7, 2018|
|1.1.1||Dec 3, 2018|
|1.1.0||Nov 2, 2018|
|1.0.2||Oct 23, 2018|
|1.0.1||Sep 25, 2018|
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]
We analyzed this package on Feb 14, 2019, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
Detected platforms: other
The package description is too short. (-13 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
build_runner_core.dart. Packages with multiple examples should provide
For more information see the pub package layout conventions.
|Dart SDK||>=2.0.0 <3.0.0|