Nate Bosch
Nate Bosch
Around here: https://github.com/dart-lang/build/blob/593931a940dfa6236c50d034e51bc00ff97f5ac0/build_runner_core/lib/src/validation/config_validation.dart#L26 We have a validation for the full `package_name:builder_name` key, but if the package doesn't exist at all we could give a more clear error.
Replaced by `webdev serve` which has it's own hot reloading handling. We should be able to remove: - The `serve` command and all related code. - All code related to...
I think this is usually done by searching upwards for an `index.html` instead of serving a 404. Hopefully we can make this an option with our handler. Otherwise we should...
Currently it's easy to go from `--release` back to dev and if nothing has changed very little work needs to be done, the DDC entrypoint builder is cheap and no...
We don't currently read this section of the config since it all happens based on the `Builder` instances. We only really require this section for `dazel` since it's needed statically...
As long as we are only checking the _user_ provided globs, and not the defaults from builders, we can probably add a warning if you've specified a `generate_for` glob that...
Warn or fail if attempting to write two different top level directories to the same output directory
`pbr build -o web:foo test:foo` will end up with just `web` output and `test` doesn't get output.
Unblocks a custom build script whose behavior won't depend on having the same version of `build_config` as all the packages in a pub solve.
The build systems run on the Dart VM only, so there are limitations on what imports can be used by builders. Add documentation describing how to work around this limitation...