Nate Bosch

Some thoughts: - We could potentially do the validation as a warning but only when it's the root package `build.yaml` - that way the author sees it but no one...

> I think we could probably have an asset reader which reads by communicating with the main isolate Yeah that's what I was thinking. If we ever end up needing...

In _theory_ we could call this a breaking change on `build_config` and packages that are doing the "right" think and have a dependency on that package whenever they use `build.yaml`...

And step 0 is make that dependency less heavy. Blocked by #2192

You can set the `BUILD_MAX_WORKERS_PER_TASK` environment variable. I'll leave this issue open to track adding something to our FAQ about this.

Makes sense, we only use the URIs for libraries, not all files. https://github.com/dart-lang/build/blob/2ea08e20c5bbc3833f501de63c9514fee77f31be/build_runner_core/lib/src/changes/build_script_updates.dart#L55-L56 I wonder if it'll slow things down too much to iterate over declarations and use source locations....

Blocked by https://github.com/dart-lang/sdk/issues/35396

> Additional one-time startup cost to compile the SDK. This would be once per "clean build" - so it would happen on every `pub upgrade` as well as SDK upgrades.

Some other options for completeness: - Stop printing stack traces by default and only print them when some option is passed - ~~Check the type, if its a subclass of...

Builders are invoked here: https://github.com/dart-lang/build/blob/04ba2196bca63a6999365d788b1cd66062f423fc/build_runner_core/lib/src/generate/build_impl.dart#L486 I would expect that special handling for this exception might involve the logging handler: https://github.com/dart-lang/build/blob/04ba2196bca63a6999365d788b1cd66062f423fc/build/lib/src/builder/logging.dart#L28