build_runner

• Use raw string literals for builder options when generating build scripts.

• Minor fixes to the log message when compiling the build script has some output.
• Drop package:pedantic dependency and replace it with package:lints.

• Support --enable-experiment option in build daemon.

• 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.

• Add --log-requests flag to build daemon.
• Log failed asset requests in build_runner server.
• Support the latest build (2.1.0).

• Allow analyzer version 2.x.x.

• Don't set the content length header or body when responding to HEAD requests.

• Allow builders defined as relative imports from the root of a package to run with sound null safety.

• Fix a serve mode bug which causes an unhandled exception if the build fails to initialize (usually because it is out of date).

• Use the frontend server to improve the performance of generating build script snapshots.

• Fix bad cast in build_runner while parsing options for daemon mode.

• Migrate to null safety.

• Update to the latest build_runner_core.

• Allow the latest dart_style.

• Allow the latest http_multi_server.

• 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

• Fix arg parsing for the clean and generate-build-script commands.

• Fix snapshot generation hanging on windows if there is anything on stdout.

• Allow the latest build_config.

• Update to glob 2.x.

• Allow the null safe pre-release version of shelf, package_config, and watcher.

• Backport of 622c659.
  • 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.

• 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.

• Allow the null safe pre-release version of stream_transform.

• 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.

• Fix handling of build.yaml generateFor default config for values including a $ such as $package$. Use raw strings in the generated build script.

• Allow build version 1.6.x.

• Allow build_config version '>=0.4.1 <0.4.6'.
• Allow yaml version '>=2.1.11 <4.0.0'.

• 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.

• Allow build_config version 0.4.3.

• 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.

• Ensure that the generated build script is opted out of null safety, even if the current package supports it.

• 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).

Unpin analyzer and set the min sdk to 2.10 to resolve the subsequent issue https://github.com/dart-lang/sdk/issues/42887.

Pin analyzer to 0.39.14 to work around Issue #2763.

• Add an --enable-experiment flag which enables running builders on code that requires a language experiment to be enabled.

• 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.

• Update to build_runner_core version ^5.0.0.
• Remove dev dependency on package_resolver.

• 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.

• 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.

• 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.

• 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.

• Allow build version 1.2.x.

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:

• <target-dir>/**
• 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 <dir> 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.

• Fix bugs in snapshot invalidation logic that prevented invalidation when core packages changed and always created a new snapshot on the second build.

• Improve the manual change detector to do a file system scan on demand instead of using a file watcher.

• Set the charset to utf-8 for Dart content returned by the AssetHandler.

• 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).

• Require package:build_config ">=0.4.1 <0.4.2". Use new API that improves error information when a build configuration file is malformed.

• Fix an issue where warning logs on startup were accidentally upgraded to severe logs in the daemon mode.

• Preemptively re-snapshot when the build_runner or build_daemon packages are updated.

• Support the latest build_daemon version.
• Expose assetServerPort as a top level helper method.

• Update the test command to wait to exit until the inner test process exits.

• Depend on the latest build_daemon and provide a shutdown notification on build script updates.

• Use a polling directory watcher by default on windows again.

• Fix an issue where exit codes were not set correctly when running the generated build script directly.

• Update to the latest build_daemon.

• Add a run command to execute VM entrypoints with generated sources.