build_runner_core 2.0.1
build_runner_core: ^2.0.1 copied to clipboard
Core tools to write binaries that run builders.
2.0.1 #
- Fix an issue where the
finalizedReaderwas notresetprior to build.
2.0.0 #
- The
buildmethod now requires a list ofbuildDirs. - Remove
buildDirsfromBuildOptions. - Added the
overrideGeneratedDirectorymethod which overrides the directory for generated outputs.- Must be invoked before creating a
BuildRunnerinstance.
- Must be invoked before creating a
1.1.3 #
- Update to
package:graphsversion0.2.0. - Allow
buildversion1.1.x. - Update the way combined input hashes are computed to not rely on ordering.
- Digest implementations must now include the AssetId, not just the contents.
- Require package:build version 1.1.0, which meets the new requirements for digests.
1.1.2 #
- Fix a
NoSuchMethodErrorthat the user could get when adding new dependencies.
1.1.1 #
- Fix a bug where adding new dependencies or removing dependencies could cause
subsequent build errors, requiring a
pub run build_runner cleanto fix.
1.1.0 #
- Support running the build script as a snapshot.
- Added new exceptions,
BuildScriptChangedExceptionandBuildConfigChangedException. These should be handled by scripts as described in the documentation. - Added new
FailureTypes ofbuildScriptChangedandbuildConfigChanged.
1.0.2 #
- Support the latest
package:json_annotation.
1.0.1 #
- Update
package:buildversion constraint to>1.0.0 <1.0.1.
1.0.0 #
Breaking Changes #
- The performance tracking apis have changed significantly, and performance
tracking now uses the
timingpackage. - The
BuildOptionsstatic factory now takes aLogSubscriptioninstead of aBuildEnvironment. Logging should be start as early as possible to catch logs emitted during setup.
New Features #
- Use the
timingpackage for performance tracking. - Added support for
BuildStep.trackStageto track performance of custom build stages within your builder.
Bug Fixes #
- Fixed a node invalidation issue when fixing build errors that could cause a situation which was only resolvable with a full rebuild.
0.3.1+5 #
- Fixed an issue where builders that didn't read their primary input would get invalidated on fresh builds when they shouldn't.
0.3.1+4 #
- Removed the constraint on reading files that output to cache from files that output to source.
0.3.1+3 #
- Bug Fix: Don't output a
packagessymlink within thepackagesdirectory.
0.3.1+2 #
- Restore
newkeyword for a working release on Dart 1 VM. - Bug Fix: Don't include any non-lib assets from dependencies in the build, even if they are a source in a target.
0.3.1+1 #
- Bug Fix: Don't include any non-lib assets from dependencies in the build, even if they are a source in a target.
- Release broken on Dart 1 VM.
0.3.1 #
- Migrated glob tracking to a specialized node type to fix dart-lang/build#1702.
0.3.0 #
Breaking Changes #
- Implementations of
BuildEnvironmentmust now implement thefinalizeBuildmethod. There is a default implementation if you extendBuildEnvironmentthat is a no-op.- This method is invoked at the end of the build that allows you to do arbitrary additional work, such as creating merged output directories.
- The
assumeTtyargument onIOEnvironmenthas moved to a named argument sincenullis an accepted value. - The
outputMapfield onBuildOptionshas moved to theIOEnvironmentclass.
New Features/Updates #
- Added a
outputSymlinksOnlyoption toIOEnvironmentconstructor, that causes the merged output directories to contain only symlinks, which is much faster than copying files. - Added the
FinalizedAssetViewclass which provides a list of all available assets to theBuildEnvironmentduring the build finalization phase.outputMaphas moved fromBuildOptionsto this constructor, as a named argument.
- The
OverridableEnvironmentnow supports overriding the newfinalizeBuildapi. - The number of concurrent actions per phase is now limited (currently to 16), which should help with memory and cpu usage for large builds.
0.2.2+2 #
- Support
package:json_annotationv1.
0.2.2+1 #
- Tag errors from cached actions when they are printed.
0.2.2 #
- Changed the default file caching logic to use an LRU cache.
0.2.1+2 #
- Clarify wording for conflicting output directory options. No behavioral differences.
- Reduce the memory consumption required to create an output dir significantly.
- Increased the upper bound for the sdk to
<3.0.0.
0.2.1+1 #
- Allow reuse cache between machines with different OS
0.2.1 #
- The hash dir for the asset graph under
.dart_tool/buildis now based on a relative path to the build script instead of the absolute path.- This enables
.dart_tool/builddirectories to be reused across different computers and directories for the same project.
- This enables
0.2.0 #
New Features #
- The
BuildPerformanceclass is now serializable, it has afromJsonconstructor and atoJsoninstance method. - Added
BuildOptions.logPerformanceDir, performance logs will be continuously written to that directory if provided. - Added support for
global_optionsinbuild.yamlof the root package. - Allow overriding the default
Resolversimplementation. - Allows building with symlinked files. Note that changes to the linked files will not trigger rebuilds in watch or serve mode.
Breaking changes #
BuildPhasePerformance.actionhas been replaced withBuildPhasePerformance.builderKeys.BuilderActionPerformance.builderhas been replaced withBuilderActionPerformance.builderKey.BuildResultno longer has anexceptionorstackTracefield.- Dropped
failOnSeverearguments. Severe logs are always considered failing.
Internal changes #
- Remove dependency on package:cli_util.
0.1.0 #
Initial release, migrating the core functionality of package:build_runner to this package.