Daco Harkes

> `flutter pub run` is deprecated and should be removed. We should only have `dart run` and `flutter run` (different resolution logic). So, if one uses for example FFIgen in...

This design would be similar to Rust/Cargo's `build.rs`, it also has a separate list of build dependencies: https://doc.rust-lang.org/cargo/reference/build-scripts.html#build-dependencies

> * We're using an experimental feature and published with SDK constraint `^3.1.0-dev` instead of `>=3.1.0-dev

> Dart Asset Collation and Organization - `daco/`? Haha, I completely missed this one earlier. 😆 How'd you come up with this! 🤣 Considering the developments in https://github.com/dart-lang/sdk/issues/54334, this should...

> I'm not sure it'd help with `package:vm_service`. The VM service target could be running on a version of the SDK that's compatible with the version of `package:vm_service` used by...

Right we talked about a similar thing yesterday. I tried to remember it this morning but couldn't come up with it. So there are multiple places where version skew between...

> private_dependencies @jonasfj Private dependencies is not entirely safe either. Because you could not leak your dependency types to the public API but leak the json-serialized format to metadata or...

Correct, I'm not so interested in cyclic dependencies. (Also, really with native assets we should not have cyclic dependencies! But who knows, if we'd support it I might start using...

> This will not be supported anytime soon That's reason for giving it a p4 or p3 label, not for closing it correct?

As a workaround: 1. `.pubignore` `test/` (Might have no bad consequences. However, it requires keeping the gitignore and pubignore in sync.) 2. `analysis_options.yaml` `exclude` `test/data/` (Undesired, it stops analysis of...