Core functionality of the build_runner package. Exposes the imperative apis
for running pure Dart builds for
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: ^0.3.1+4
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:
|0.3.1+4||Aug 13, 2018|
|0.3.1+3||Aug 13, 2018|
|0.3.1+2||Aug 10, 2018|
|0.3.1+1||Aug 9, 2018|
|0.3.1||Aug 7, 2018|
|0.3.0||Aug 1, 2018|
|0.2.2+2||Jul 24, 2018|
|0.2.2||Jul 18, 2018|
|0.2.1+2||Jul 16, 2018|
|0.2.1+1||Jul 6, 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 Aug 13, 2018, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
Detected platforms: other
The description is too short.
Add more detail about the package, what it does and what is its target use case. Try to write at least 60 characters.
Package is pre-v1 release.
While there is nothing inherently wrong with versions of
0.*.*, it usually means that the author is still experimenting with the general direction of the API.
Maintain an example.
Create a short demo in the
example/ directory to show how to use this package. Common file name patterns include:
example.dart or you could also use
|Dart SDK||>=2.0.0 <3.0.0|