Daco Harkes

> Could it be `ffi_build.dart`, `ffi_link.dart`? That's specific enough to be precise. I might even understand what it is :) @mosuem wants to use the (to be built) `link.dart` to...

We require these scripts to be dart scripts. We can use the "current" Dart executable to run these scripts from where we want to run them. We could require the...

> Do current build stack and web compilers migrate to this? Web frameworks should _not_ use a `build.dart` internally. Dart command-line and Flutter apps consume the output of `build.dart` so...

I love the idea of having a place to hook in to for making sure all generated code is indeed regenerated before `dart pub publish` publishes the files. If we...

Based on the discussion in this issue and related issues, the two most probable options are: 1. `scripts/build.dart`, `script/link.dart`, etc. and we'd reserve the whole script folder. All scripts would...

> Then consider whether it can be a subdirectory of `tool` instead of a top-level directory. One issue with making it a subdirectory is the discoverability. If we're going to...

So, are we going for `hook/`?

I have updated the issue description to say that we are reserving the `hook/` toplevel directory. @itsjustkevin This is ready to go through the breaking change approval queue.

Drive by comment. We might be trying to solve similar use cases in the work on "native assets" (https://github.com/flutter/flutter/issues/129757), data assets (https://github.com/dart-lang/native/issues/154), and `hook/link.dart` (https://github.com/dart-lang/native/issues/153). Maybe we're trying to solve...

> > > Users author Dart packages that transform a file. These packages follow two rules: 1) they accept (the location of) an input file via an `--input` option, and...