## 2.13.1 - Allow `analyzer` 11.0.0 and 12.0.0. ## 2.13.0 - Performance: speedup of between 1.4x for small initial builds to 4x for large incremental builds. See https://github.com/dart-lang/build/pull/4405 for full benchmark results. Optimizations included: faster management of files for analysis, re-use syntax errors computation, avoid a throw/catch on "not yet generated" source, copy asset graph without a serialization round trip, re-use trigger configuration digest. - Add `--dart-aot-perf` flag for profiling on Linux. Use it with `--force-aot`. It runs the builders under the `perf` profiling tool which writes to `perf.data`. - Add `--verbose-durations` flag that logs durations with greater precision. - Improve debugging instructions in README.md. - Bug fix: fix line wrapping in `build_runner` args usage output. ## 2.12.2 - Bug fix: don't crash if `applies_builders` in `build.yaml` mentions an unknown builder. ## 2.12.1 - Require `build_config` 1.3.0. ## 2.12.0 - Add support for globs in the package list of workspace `pubspec.yaml`, matching the new feature in Dart SDK `3.11`. - Support the `build_to` key added to `post_process_builders` in `build_config 1.3.0`. Post process builders can use this to output files to the source tree. - Bug fix: prevent logging crash when using `build_test` in a builder. ## 2.11.1 - Improve logging on build script build failures, don't repeatedly log an identical failure. - Bug fix: with `--workspace` flag, correctly build for sources in the workspace root instead of failing with "tried to delete from package not in the build". ## 2.11.0 - Add `--workspace` flag. Use it with `dart run build_runner build` or `watch` to build or watch or all packages in the current workspace. It is currently experimental and subject to change based on feedback, please add feedback at https://github.com/dart-lang/build/discussions/4349. - Bug fix: fix crash in corner case with post process builder, optional builder and output used for `--output`, `watch` or `serve`. - Bug fix: fix crash in corner case with `watch` or `serve` when builders depend on generated files in the current build. ## 2.10.5 - Add logging of builder compilation so you can tell how much time is spent on the JIT or AOT compile. Explicitly log restarts to recompile builders. - Allow `analyzer` 10.0.0. ## 2.10.4 - Allow `analyzer` 9.0.0. ## 2.10.3 - Performance: improve scalability with the number of library cycles, making builds much faster for some large codebases. - Bug fix: fix crash when you run `dart run build_runner build` in a subdirectory of a package. - Bug fix: in a workspace, generate for transitive dependencies of the current package instead of for all packages in the workspace. ## 2.10.2 - Bug fix: fix issue with webdev failing due to a modification during a build. - In "serve" and "watch" modes, retry failed compiles instead of exiting. ## 2.10.1 - Performance: improve `findAssets` scalability, making it much faster for prefix matches in packages with thousands of files or more. One specific use case that is now faster is builders that use `source_gen` shared parts, for example `built_value` and `json_serializable`. - Bug fix: look up triggers in the `triggers` section of `build.yaml` using the full name. For the case in which the builder name matched the package name, the abbreviated name was being used instead. - Bug fix: fix incorrect log `with build_runner/aot` on Windows with JIT. ## 2.10.0 - Add AOT compilation of builders. A future release will AOT compile builders automatically, for this release it's behind a flag. AOT compiled builders start up faster and have higher throughput, for faster builds overall. Builders that use `dart:mirrors` cannot be AOT compiled. - Add `force-aot` flag to AOT compile builders. - Add `force-jit` flag to force the current default of JIT compiling builders. - Add the `--dart-jit-vm-arg` option. Its values are passed to `dart run` when a build script is started in JIT mode. This allows specifying options to attach a debugger to builders. - Require `analyzer` 8.0.0. Remove use of deprecated `analyzer` members, use their recommended and compatible replacements. - Internal changes for `build_test`. ## 2.9.0 - Watch mode: handle builder config changes without recompiling or exiting. - Remove log output about `build_runner` internals. - Print the port that gets picked if you pass 0 for a port number, for example with `dart run build_runner serve web:0`. - Improve warnings when an option is specified for an unknown builder. - Rewrite bootstrap code to remove use of `dart:mirrors`. - Bug fix: require `args` 2.5.0. ## 2.8.0 - Make errors more prominent in log output, highlight in red. - Remove "deleting declared outputs" warning. - Bug fix: fix incorrect display of some "usage" messages. - Move code from `build_resolvers` into `build_runner`. - Move code from `build_runner_core` into `build_runner`. - Move code from `timing` into `build_runner`. - Remove unused deps: `build_resolvers`, `build_runner_core`, `timing`. ## 2.7.2 - Use `build` 4.0.0. ## 2.7.1 - Bug fix: with `build_runner serve`, special handling of paths containing `/packages/` was hiding actual folders called `packages`. Serve the actual folders first, before trying the package lookup. - Remove undocumented / unused features: `lib/build_script_generate.dart`, `bin/graph_inspector.dart`, `build_runner doctor` and `build_runner generate-build-script` commands. - Remove deps on `pubspec_parse` and `timing`. - Use `build` 3.1.0. ## 2.7.0 - Performance: builders can choose to run only when "triggered". A builder runs only if triggered if the option `run_only_if_triggered` is `true`. Triggers are configured in new a top-level section of `build.yaml` called `triggers`. See [the `build_config` docs](https://pub.dev/packages/build_config#triggers) for more information. - Remove interactive prompts for whether to delete files. - Ignore `-d` flag: always delete files as if `-d` was passed. - Remove `--use-polling-watcher` flag. - Remove `build_runner serve` mode `$graph` and `$perf` handlers. - Documentation revamp. - Bug fix: delete transitive generated outputs as well as direct generated outputs. So, a generated file now gets deleted if its input was a generated file that is no longer output. - Bug fix: fix crash creating a merged output dir with a file called `lib`. ## 2.6.1 - Use `build` 3.0.1. ## 2.6.0 - Remove unused deps: `analyzer`, `build_resolvers`, `collection`, `http`, `js`, `meta`, `package_config`, `pool`, `web`, `yaml`. - Remove unused dev_deps: `http`, `package_config`, `web`. - Testing: read build configs using `AssetReader` so they're easier to test. - Use `build` 3.0.0. - Use `build_resolvers` 3.0.0. ## 2.6.0-dev.2 - Remove unused deps: `analyzer`, `build_resolvers`, `collection`, `http`, `js`, `meta`, `package_config`, `pool`, `web`, `yaml`. - Remove unused dev_deps: `http`, `package_config`, `web`. - Testing: read build configs using `AssetReader` so they're easier to test. ## 2.6.0-dev.1 - Use `build` 3.0.0-dev. - Use `build_resolvers` 3.0.0-dev. ## 2.5.4 - Bug fix: fix incremental build when previous build had `package:` import of a missing dep or a missing file. ## 2.5.3 - Bug fix: fix corner case with checked in generated output that could cause a crash. - Bug fix: during initial build cleanup, really delete files that correspond to hidden generated files. ## 2.5.2 - Simplify warnings for outdated `analyzer`. ## 2.5.1 - Don't log stack traces for subclasses of `Exception`. - Bug fix: don't run builders with multiple outputs once per output. ## 2.5.0 User-visible changes: - Improved performance for large builds. More performance improvements will follow, if your workflow is affected by slow `build_runner` performance then please consider sharing details at https://github.com/dart-lang/build/discussions. - Improved logging: show what builders are running and, for long-running builders, where the time is spent. Versions: - Bump the min SDK to 3.7.0. - Use `build_test` 3.0.0. - Use `build_runner_core` 9.0.0. Internal changes: - Start using `package:build/src/internal.dart'. - Refactor `MultiPackageAssetReader` to internal `AssetFinder`. - `FinalizedReader` no longer implements `AssetReader`. - Refactor `CachingAssetReader` to `FilesystemCache`. - Refactor `FileBasedAssetReader` and `FileBasedAssetWriter` to `ReaderWriter`. - Remove `OnDeleteWriter`, add functionality to `ReaderWriter`. - Add `NodeType` to `AssetNode`, remove subtypes. Make mutations explicit. - Use `built_value` for `AssetNode` and related types. - Add details of what changed and what is built to `--verbose` logging. - Compute outputs as needed instead of storing them in the asset graph. - Refactor invalidation to track current build progress in `Build` instead of in the asset graph. - Remove `completeBuild` from `RunnerAssetWriter` as it's no longer needed. ## 2.4.15 - Update to package:web and dart:js_interop. - Support the latest `package:shelf_web_socket`. - Add hidden `--use-experimental-resolver` flag for issue #3811 performance work. This flag will be removed. ## 2.4.14 - Write generated assets at the end of a build to avoid invalidating other tools with a file watcher multiple times. - Bump the min sdk to 3.6.0. - Allow analyzer version 7.x. - Hard code the generated build script to language version 3.6. - Allow dart_style version 4.0.0, require at least 2.3.7. ## 2.4.13 - Bump the min sdk to 3.5.0. - Bump the `mime` dependency to allow version 2.x. ## 2.4.12 - Bump the min sdk to 3.5.0-259.0.dev. - Fix watch mode for workspace repos. ## 2.4.11 - Explicitly pass the current isolates package config instead of assuming the location, to support the upcoming pub workspaces feature. ## 2.4.10 - Support version `1.x` and `2.x` of `shelf_web_socket` and `2.x` and `3.x` - of `web_socket_channel`. - Bump the min sdk to 3.4.0. ## 2.4.9 - Update the `package:frontend_server_client` constraint to `>=3.0.0 <5.0.0`. ## 2.4.8 - Update README.md to point to the FAQ and other docs. - Print stack traces for `Error` subtype exceptions in non-verbose mode. - Support latest version of `package:js`. ## 2.4.7 - Fix broken link in README.md. - Bump the min sdk to 3.0.0. - Add a warning to the `doctor` command if a `build.yml` file is found (instead of a `build.yaml` file). ## 2.4.6 - Allow the latest analyzer (6.x.x). ## 2.4.5 - Fix a bug handling a builder which has a `required_input` that matches it's own output. ## 2.4.4 - Use a stable order for builders without an order defined by dependencies. ## 2.4.3 - Make the `doctor` command visible. ## 2.4.2 - Support package:build version 2.4.x. ## 2.4.1 - Mention --build-filter option in the README. - Update to build_daemon 4.0. - Support enabling experiments in build scripts. ## 2.4.0 - Warn if a `package:` builder import cannot be resolved and skip it, instead of creating an invalid build script or failing in other obscure ways. - Require Dart 3.0, drop support for unsound build scripts. ## 2.3.3 - Remove references to `NullThrownError`. ## 2.3.2 - Add supported platforms to pubspec. ## 2.3.1 - Upgrade to `frontend_service_client` version 3. ## 2.3.0 - Add `-d` as a shorthand for `--delete-conflicting-outputs`. ## 2.2.1 - Allow the latest `package:analyzer`. - Stop ignoring the no_leading_underscores_for_library_prefixes lint in generated build scripts, code_builder now does this for you. ## 2.2.0 - Support global 'runs_before' configuration for builders. This allows users to influence the ordering of builders in their build. ## 2.1.11 - Stop reading or requiring `.packages` files. - Use an explicit `dynamic` generic type for collections in default builder options to reduce behavior differences between reading default options and user provided options. ## 2.1.10 - Allow build version 2.3.x. ## 2.1.9 - Fix up the formatting a bit for the error message that is logged when we get errors from the directory watcher. - Ignore the no_leading_underscores_for_library_prefixes lint in the generated build script. - Report changed assets when running as a deamon. - Allow analyzer version 4.x. ## 2.1.8 - Support null stack traces coming from the build runner script isolate. ## 2.1.7 - Allow the latest `pkg:build`. ## 2.1.6 - Allow the latest analyzer. ## 2.1.5 - Use raw string literals for builder options when generating build scripts. ## 2.1.4 - Minor fixes to the log message when compiling the build script has some output. - Drop package:pedantic dependency and replace it with package:lints. ## 2.1.3 - Use `dart` top level command instead of `pub` when running pub executables. ## 2.1.2 - Support `--enable-experiment` option in build daemon. ## 2.1.1 - Don't rethrow file watcher errors - instead log at severe level and continue going. The file watcher implementation should restart automatically as of package:watcher version `0.9.7+13`. ## 2.1.0 - Add `--log-requests` flag to build daemon. - Log failed asset requests in build_runner server. - Support the latest build (`2.1.0`). ## 2.0.6 - Allow analyzer version 2.x.x. ## 2.0.5 - Don't set the content length header or body when responding to HEAD requests. ## 2.0.4 - Allow builders defined as relative imports from the root of a package to run with sound null safety. ## 2.0.3 - Fix a serve mode bug which causes an unhandled exception if the build fails to initialize (usually because it is out of date). ## 2.0.2 - Use the frontend server to improve the performance of generating build script snapshots. ## 2.0.1 - Fix bad cast in build_runner while parsing options for daemon mode. ## 2.0.0 - Migrate to null safety. - Update to the latest `build_runner_core`. ## 1.12.2 - Allow the latest `dart_style`. ## 1.12.1 - Allow the latest `http_multi_server`. ## 1.12.0 - Remove support for hot-reloads. Use `package:webdev` instead. - Support version 2.0.x of the `build` package - Update to graphs `1.x` - Support version `1.x` of `shelf_web_socket` and `2.x` of `web_socket_channel` ## 1.11.5 - Fix arg parsing for the `clean` and `generate-build-script` commands. ## 1.11.4 - Fix snapshot generation hanging on windows if there is anything on stdout. ## 1.11.3 - Allow the latest `build_config`. ## 1.11.2 - Update to glob `2.x`. ## 1.11.1+1 - Backport of [622c659](https://github.com/dart-lang/build/commit/622c659d6dfcb982d599d6dddbd9988b25a064a1). - Don't rethrow file watcher errors - instead log at severe level and continue going. The file watcher implementation should restart automatically as of package:watcher version `0.9.7+13`. ## 1.11.1 - Allow the null safe pre-release version of `shelf`, `package_config`, and `watcher`. ## 1.11.0 - Support generating custom build scripts through `package:build_runner/build_script_generate.dart`: - Export `generateAndRun` to snapshot and run build scripts. - Export `findBuilderApplications` to find builder applications from a package graph. ## 1.10.13 - Allow the null safe pre-release version of `stream_transform`. ## 1.10.12 - Allow the null safe pre-releases of all migrated deps. - Add a warning if a `builders` section is found in when parsing an overridden build.yaml file via the `--config` flag. ## 1.10.11 - Fix handling of `build.yaml` `generateFor` default config for values including a `$` such as `$package$`. Use raw strings in the generated build script. ## 1.10.10 - Allow build version `1.6.x`. ## 1.10.9 - Allow build_config version `'>=0.4.1 <0.4.6'`. - Allow yaml version `'>=2.1.11 <4.0.0'`. ## 1.10.7 - Allow build_config version 0.4.4. - Fix a daemon mode issue where we might try to complete a completer twice during build script updates. ## 1.10.6 - Allow build_config version 0.4.3. ## 1.10.5 - Better handle the case where the package config file is deleted while the watcher is running, by waiting for up to 1 second for it to be written again before failing. ## 1.10.4 - Ensure that the generated build script is opted out of null safety, even if the current package supports it. ## 1.10.3 - Remove high sdk constraint, allow >=2.9.0. - Require latest build_resolvers (which requires the latest analyzer). - Require the latest build version (1.5.x). ## 1.10.2 Unpin analyzer and set the min sdk to 2.10 to resolve the subsequent issue https://github.com/dart-lang/sdk/issues/42887. ## 1.10.1 Pin `analyzer` to `0.39.14` to work around Issue #2763. ## 1.10.0 - Add an `--enable-experiment` flag which enables running builders on code that requires a language experiment to be enabled. ## 1.9.0 - Add a warning if a package is missing some required placeholder files, including `$package$` and `lib/$lib$`. - Reduce chances for changing apparent build phases across machines with a different order of packages from `package_config.json`. ## 1.8.1 - Update to `build_runner_core` version `^5.0.0`. - Remove dev dependency on `package_resolver`. ## 1.8.0 - Kill the watcher script when we see edits to the package_config.json file in the same way that we already do for the .packages file. ## 1.7.4 - Give a warning instead of a stack trace when using a build config override file for a package that does not exist. - Allow the latest build_config version. ## 1.7.3 - Improve the error message when a `--hostname` argument is invalid. - Require SDK version `2.6.0` to enable extension methods. - Allow the latest `stream_transform`. ## 1.7.2 - Enable the native windows directory watcher by default. - Added a --use-polling-watcher option which overrides this to use a polling watcher again. - Increased the lower bound for the SDK to a version which contains various fixes for the native windows directory watcher. - Give a more consistent ordering for Builders when their ordering is allowed to be arbitrary. - Handle more `--help` invocations without generating the build script. ## 1.7.1 - Allow `build` version 1.2.x. ## 1.7.0 ### New Feature: Build Filters Build filters allow you to choose explicitly which files to build instead of building entire directories. A build filter is a combination of a package and a path, with glob syntax supported for each. Whenever a build filter is provided, only required outputs matching one of the build filters will be built, in addition to the inputs to those outputs. ### Command Line Usage Build filters are supplied using the new `--build-filter` option, which accepts relative paths under the package as well as `package:` uris. Glob syntax is allowed in both package names and paths. **Example**: The following would build and serve the JS output for an application, as well as copy over the required SDK resources for that app: ``` pub run build_runner serve \ --build-filter="web/main.dart.js" \ --build-filter="package:build_web_compilers/**/*.js" ``` ### Build Daemon Usage The build daemon now accepts build filters when registering a build target. If no filters are supplied these default filters are used, which is designed to match the previous behavior as closely as possible: - `/**` - `package:*/**` **Note**: There is one small difference compared to the previous behavior, which is that build to source outputs from other top level directories in the root package will no longer be built when they would have before. This should have no meaningful impact other than being more efficient. ### Common Use Cases **Note**: For all the listed use cases it is up to the user or tool the user is using to request all the required files for the desired task. This package only provides the core building blocks for these use cases. #### Testing If you have a large number of tests but only want to run a single one you can now build just that test instead of all tests under the `test` directory. This can greatly speed up iteration times in packages with lots of tests. **Example**: This will build a single web test and run it: ``` pub run build_runner test \ --build-filter="test/my_test.dart.browser_test.dart.js" \ --build-filter="package:build_web_compilers/**/*.js" \ -- -p chrome test/my_test.dart ``` **Note**: If your test requires any other generated files (css, etc) you will need to add additional filters. #### Applications This feature works as expected with the `--output ` and the `serve` command. This means you can create an output directory for a single application in your package instead of all applications under the same directory. The serve command also uses the build filters to restrict what files are available, which means it ensures if something works in serve mode it will also work when you create an output directory. ## 1.6.9 - Fix bugs in snapshot invalidation logic that prevented invalidation when core packages changed and always created a new snapshot on the second build. ## 1.6.8 - Improve the manual change detector to do a file system scan on demand instead of using a file watcher. ## 1.6.7 - Set the `charset` to `utf-8` for Dart content returned by the `AssetHandler`. ## 1.6.6 - Added watch event debouncing to the `daemon` command to line up with the `watch` command. This makes things work more nicely with swap files as well as "save all" type scenarios (you will only get a single build most times). ## 1.6.5 - Require `package:build_config` `">=0.4.1 <0.4.2"`. Use new API that improves error information when a build configuration file is malformed. ## 1.6.4 - Fix an issue where warning logs on startup were accidentally upgraded to severe logs in the daemon mode. ## 1.6.3 - Preemptively re-snapshot when the `build_runner` or `build_daemon` packages are updated. ## 1.6.2 - Support the latest `build_daemon` version. - Expose `assetServerPort` as a top level helper method. ## 1.6.1 - Update the `test` command to wait to exit until the inner test process exits. ## 1.6.0 - Depend on the latest `build_daemon` and provide a shutdown notification on build script updates. ## 1.5.2 - Use a polling directory watcher by default on windows again. ## 1.5.1 - Fix an issue where exit codes were not set correctly when running the generated build script directly. ## 1.5.0 - Update to the latest `build_daemon`. ## 1.4.0 - Add a `run` command to execute VM entrypoints with generated sources. ## 1.3.5 - Use the latest `build_daemon`. ## 1.3.4 - Use the latest `build_config`. ## 1.3.3 - Use `HttpMultiServer.loopback` for the daemon asset server. ## 1.3.2 - Fix an error where daemon mode would claim support for prompts when it can't actually support them and would hang instead. - Improve logging when the daemon fails to start up, previously no logs would be shown. ## 1.3.1 - Remove usage of set literals to fix errors on older sdks that don't support them. ## 1.3.0 - Fix an issue where we might re-use stale build snapshots, which could only be resolved by deleting the `.dart_tool` dir (or doing a `clean`). - Depend on the latest `build_runner_core` and `build_daemon` releases. ## 1.2.8 - Fix issue where daemon command wouldn't properly shutdown. - Allow running when the root package, or a path dependency, is named `test`. ## 1.2.7 - Fix issue where daemon command would occasionally color a log. ## 1.2.6 - Prevent terminals being launched when running the daemon command on Windows. - No longer assumeTty when logging through the daemon command. - Update `build_daemon` to version `0.4.0`. - Update `build_runner_core` to version `2.0.3`. - Ensure the daemon command always exits. ## 1.2.5 - Fix a bug with the build daemon where the output options were ignored. ## 1.2.4 - Update `build_resolvers` to version `1.0.0`. ## 1.2.3 - Fix a bug where changing between `--live-reload` and `--hot-reload` might not work due to the etags for the injected JS not changing when they should. ## 1.2.2 - Change the format of Build Daemon messages. - Build Daemon asset server now properly waits for build results. - Build Daemon now properly signals the start of a build. - Fix path issues with Daemon command under Windows. ## 1.2.1 - Update `package:build_runner_core` to version `2.0.1`. ## 1.2.0 - Support building through `package:build_daemon`. - Update `package:build_runner_core` to version `2.0.0`. ## 1.1.3 - Update to `package:graphs` version `0.2.0`. - Fix an issue where when running from source in watch mode the script would delete itself when it shouldn't. - Add digest string to the asset graph visualization. - Added a filter box to the asset graph visualization. - Allow `build` version `1.1.x`. ## 1.1.2 - Improve error message when the generated build script cannot be parsed or compiled and exit with code `78` to indicate that there is a problem with configuration in the project or a dependency's `build.yaml`. ## 1.1.1 ### Bug Fixes - Handle re-snapshotting the build script on SDK updates. - Suppress header for the `Bootstrap` logger. ## 1.1.0 ### New Features - The build script will now be ran from snapshot, which improves startup times. - The build script will automatically re-run itself when the build script is changed, instead of requiring the user to re-run it manually. ## 1.0.0 ### Breaking Changes - Massive cleanup of the public api. The only thing exported from this package is now the `run` method. The goal is to reduce the surface area in order to stabilize this package, since it is directly depended on by all users. - Removed all exports from build_runner_core, if you are creating a custom build script you will need to import build_runner_core directly and add a dependency on it. - Stopped exporting the `build` and `watch` functions directly, as well as the `ServeHandler`. - If this has broken your use case please file an issue on the package and request that we export the api you were using previously. These will be considered on an individual basis but the bar for additional exports will be high. - Removed support for the --[no-]assume-tty command line argument as it is no longer needed. ## 0.10.3 - Improve performance tracking and visualization using the `timing` package. - Handle bad asset graph in the `clean` command. ## 0.10.2 - Added `--hot-reload` cli option and appropriate functionality. - Removed dependency on cli_util. ## 0.10.1+1 - Added better error handling when a socket is already in use in `serve` mode. ## 0.10.1 - Added `--live-reload` cli option and appropriate functionality - Migrated glob tracking to a specialized node type to fix dart-lang/build#1702. ## 0.10.0 ### Breaking Changes - Implementations of `BuildEnvironment` must now implement the `finalizeBuild` method. There is a default implementation if you extend `BuildEnvironment` that 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 `assumeTty` argument on `IOEnvironment` has moved to a named argument since `null` is an accepted value. - The `outputMap` field on `BuildOptions` has moved to the `IOEnvironment` class. ### New Features/Updates - Added a `outputSymlinksOnly` option to `IOEnvironment` constructor, that causes the merged output directories to contain only symlinks, which is much faster than copying files. - Added the `FinalizedAssetView` class which provides a list of all available assets to the `BuildEnvironment` during the build finalization phase. - `outputMap` has moved from `BuildOptions` to this constructor, as a named argument. - The `OverridableEnvironment` now supports overriding the new `finalizeBuild` api. - 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.9.2 - Changed the default file caching logic to use an LRU cache. ## 0.9.1+1 - Increased the upper bound for the sdk to `<3.0.0`. ## 0.9.1 - The hash dir for the asset graph under `.dart_tool/build` is now based on a relative path to the build script instead of the absolute path. - This enables `.dart_tool/build` directories to be reused across different computers and directories for the same project. ## 0.9.0 ### New Features - Added the `--log-performance ` option which will dump performance information to `` after each build. - The `BuildPerformance` class is now serializable, it has a `fromJson` constructor and a `toJson` instance method. - Added support for `global_options` in `build.yaml` of the root package. - Allow overriding the default `Resolvers` implementation. - Allows building with symlinked files. Note that changes to the linked files will not trigger rebuilds in watch or serve mode. ### Breaking changes - `BuildPhasePerformance.action` has been replaced with `BuildPhasePerformance.builderKeys`. - `BuilderActionPerformance.builder` has been replaced with `BuilderActionPerformance.builderKey`. - `BuildResult` no longer has an `exception` or `stackTrace` field. - The 'test' command through `run` will no longer set an exit code. All manual build scripts which call `run` should use the `Future` return to set the exit code for the process. - Dropped `failOnSevere` arguments and `--fail-on-severe` flag. Severe logs are always considered failing. - Severe level logs now go to `stdout` along with other logs rather than `stderr`. Uncaught exceptions from the `build_runner` system itself still go to `stderr`. ## Other - Updated to the latest camel case constants from the sdk. - Minimum sdk version is now `>=2.0.0-dev.61`. ## 0.8.10 - All builders with `build_to: source` will now be ran regardless of which directory is currently being built, see https://github.com/dart-lang/build/issues/1454 for context. - `build` will now throw instead of returning a failed build result if nothing was built. - Improve error message when a dependency has a bad `build.yaml` with a missing dependency. - Sources that are not a part of a `target` will no longer appear in the asset graph, so they will not be readable or globbable. - Updated the generated build script to not rely on json encode/decode for the builder options object. Instead it now directly inlines a map literal. ## 0.8.9 - Added support for building only specified top level directories. - The `build`, `watch` commands support positional arguments which are the directories to build. For example, `pub run build_runner build web` will only build the `web` directory. - The `serve` command treats positional args as it did before, except it will only build the directories you ask it to serve. - The `test` command will automatically only build the `test` directory. - If using the `-o` option, with the `:` syntax, then the `` will be added to the list of directories to build. - If additional directories are supplied with positional arguments, then those will also be built. - Update to latest analyzer and build packages. - Updated the `serve` logic to only serve files which were part of the actual build, and not stale assets. This brings the semantics exactly in line with what would be copied to the `-o` output directory. ## 0.8.8 - Improve search behavior on the `/$graph` page. Users can now query for paths and `AssetID` values – `pkg_name|lib/pkg_name.dart`. - Commands that don't support trailing args will now appropriately fail with a usage exception. - Fix a bug where some rebuilds would not happen after adding a new file that has outputs which were missing during the previous build. - Fix a bug where failing actions which are no longer required can still cause the overall build to fail. ## 0.8.7 - Improve error handling on the `/$graph` page. - Support the latest `package:build` ## 0.8.6 - Forward default options for `PostProcessBuilder`s in the generated build script. - If a build appears to be not making progress (no actions completed for 15 seconds), then a warning will now be logged with the pending actions. - Now fail when a build is requested which does not build anything. - Clean up some error messages. ## 0.8.5 - Add log message for merged output errors. ## 0.8.4 - Log the number of completed actions on successful builds. - Support the new `isRoot` field for `BuilderOptions` so that builders can do different things for the root package. - Deprecated `PostProcessBuilder` and `PostProcessBuildStep`. These should be imported from `package:build` instead. ## 0.8.3 - Clean and summarize stack traces printed with `--verbose`. - Added a `clean` command which deletes generated to source files and the entire build cache directory. - Bug Fix: Use the same order to compute the digest of input files to a build step when writing it as when comparing it. Previously builds would not be pruned as efficiently as they can be because the inputs erroneously looked different. ## 0.8.2+2 - The `.packages` file is now always created in the root of the output directory instead of under each top level directory. ## 0.8.2+1 - Bug Fix: Correctly parse Window's paths with new `--output` semantics. ## 0.8.2 - Allow passing multiple `--output` options. Each option will be split on `:`. The first value will be the root input directory, the second value will be the output directory. If no delimiter is provided, all resources will be copied to the output directory. - Allow deleting files in the post process build step. - Bug Fix: Correctly include the default allow list when multiple targets without include are provided. - Allow logging from within a build factory. - Allow serving assets from successful build steps if the overall build fails. - Add a `--release` flag to choose the options from `release_options` in `build.yaml`. This should replace the need to use `--config` pointing to a release version of `build.yaml`. ## 0.8.1 - Improved the layout of `/$perf`, especially after browser window resize. - `pub run build_runner` exits with a error when invoked with an unsupported command. - Bug Fix: Update outputs in merged directory for sources which are not used during the build. For example if `web/index.html` is not read to produce any generated outputs changes to this file will now get picked up during `pub run build_runner watch --output build`. - Don't allow a thrown exception from a Builder to take down the entire build process - instead record it as a failed action. The overall build will still be marked as a failure, but it won't crash the process. ## 0.8.0 ### New Features - Added the new `PostProcessBuilder` class. These are not supported in bazel, and are different than a normal `Builder` in some fundamental ways: - They don't have to declare output extensions, and can output any file as long as it doesn't conflict with an existing one. This is only checked at build time. - They can only read their primary input. - They will not cause optional actions to run - they will only run on assets that were built as a part of the normal build. - They can not be optional themselves, and can only output to cache. - Because they all run in a single phase, after other builders, none of their outputs can be used as inputs to any actions. - Added `applyPostProcess` method which takes `PostProcessBuilderFactory`s instead of `BuilderFactory`s. ### Breaking Changes - `BuilderApplication` now has a `builderActionFactories` getter instead of a `builderFactories` getter. - The default constructor for `BuilderApplication` has been replaced with `BuilderApplication.forBuilder` and `BuilderApplication.forPostProcessBuilder`. ## 0.7.14 - Warn when using `--define` or `build.yaml` configuration for invalid builders. ## 0.7.13+1 - Fix a concurrent modification error when using `listAssets` when an asset could be written. ## 0.7.13 - Fix a bug where a chain of `Builder`s would fail to run on some outputs from previous steps when the generated asset did not match the target's `sources`. - Added support for serving on IPv4 loopback when the server hostname is 'localhost' (the default). - Added support for serving on any connection (both IPv4 and IPv6) when the hostname is 'any'. - Improved stdout output. ## 0.7.12 - Added the `--log-requests` flag to the `serve` command, which will log all requests to the server. - Build actions using `findAssets` will be more smartly invalidated. - Added a warning if using `serve` mode but no directories were found to serve. - The `--output` option now only outputs files that were required for the latest build. Previously when switching js compilers you could end up with ddc modules in your dart2js output, even though they weren't required. See https://github.com/dart-lang/build/issues/1033. - The experimental `create_merged_dir` binary is now removed, it can't be easily supported any more and has been replaced by the `--output` option. - Builders which write to `source` are no longer guaranteed to run before builders which write to `cache`. - Honors `runs_before` configuration from Builder definitions. - Honors `applies_builders` configuration from Builder definitions. ## 0.7.11+1 - Switch to use a `PollingDirectoryWatcher` on windows, which should fix file watching with the `--output` option. Follow along at https://github.com/dart-lang/tools/issues/1713 for more details. ## 0.7.11 - Performance tracking is now disabled by default, and you must pass the `--track-performance` flag to enable it. - The heartbeat logger will now log the current number of completed versus scheduled actions, and it will log once a second instead of every 5 seconds. - Builds will now be invalidated when the dart SDK is updated. - Fixed the error message when missing a build_test dependency but trying to run the `test` command. - The build script will now exit on changes to `build.yaml` files. ## 0.7.10+1 - Fix bug where relative imports in a dependencies build.yaml would break all downstream users, https://github.com/dart-lang/build/issues/995. ## 0.7.10 ### New Features - Added a basic performance visualization. When running with `serve` you can now navigate to `/$perf` and get a timeline of all actions. If you are experiencing slow builds (especially incremental ones), you can save the html of that page and attach it to bug reports! ### Bug Fixes - When using `--output` we will only clean up files we know we previously output to the specified directory. This should allow running long lived processes such as servers in that directory (as long as they don't hold open file handles). ## 0.7.9+2 - Fixed a bug with build to source and watch mode that would result in an infinite build loop, [#962](https://github.com/dart-lang/build/issues/962). ## 0.7.9+1 - Support the latest `analyzer` package. ## 0.7.9 ### New Features - Added command line args to override config for builders globally. The format is `--define "=