MichealReed

> * [@mosuem](https://github.com/mosuem) prefers a flat list with targets that treats `android`, `ios`, `linux`, `macos`, `web`, `windows` as all equals instead of nesting the native oses together. I agree with...

> That's probably a non-goal, as we want to have developers build per asset type, not platform, to make build hooks as SDK agnostic as possible (is WASM part of...

> So, for JS-assets we don't really need to know if the `web_target` is `js` or `wasm_gc`. We might not need to know this for either with a way to...

Continued here > I believe @mosuem's issue would be solved by https://github.com/flutter/flutter/pull/164094#discussion_r2003507508, please let me know if it doesnt. Yes, this allows use of the asset. The concept behind #2108...

> Can you clarify what you are asking for? Are there libraries that your application depends on that webdev reports are invalid for the web and blocks compilation? Can you...

I understand the choice to restrict this but disagree, developers should have the choice as it is entirely possible to use a library with restricted dependencies with flutter. The behavior...

> If I understand your request correctly, you would like a mechanism to allow compilation of applications that contain imports of libraries that are not supported on the target platform....

> While we don't make it _easy_, it is very much possible to write a platform agnostic package, which has a single import yet works on all platforms it supports...

> This is not accurate, it looks at the imports not the dependencies. There are actual imports to `dart:io` in this case. It supports conditional imports etc fully. Was mistaken...

> Could we have a compile mode you can turn on where we replace `dart:io` with the platform-suitable package of your choice? A way through pubspec to upsert dependencies is...