Jonas Finnemann Jensen

Looking at `uni_links` I think we might not be handling federated plugins correctly. I'm pretty sure that `flutter.plugin.platforms.web.default_package` causes some stuff to be generated, and our import analysis does not...

I guess technically a federated plugin like `uni_links` can be used with wasm, it's just that you'd have to write your own platform implementation :see_no_evil: (not suggesting that the classification...

Yeah, but if I have to choose between false-positive / and true-negative, then in the case of platform tagging, false-positive isn't the worst. But yes, we need to do better...

> intl: false positive > The package still seems to use [dart:html](https://github.com/search?q=repo%3Adart-lang%2Fi18n+dart%3Ahtml+path%3A%2F%5Epkgs%5C%2Fintl%5C%2Flib%5C%2F%2F&type=code) I'm actually not sure this is a false-positive. We allow importing `dart:html` as long as it's not in...

Please file again pana. But really `package:logger` doesn't conditionally import `dart:io`. https://github.com/SourceHorizon/logger/blob/main/lib/src/outputs/advanced_file_output_stub.dart#L2 The problem is that importing `dart:io` on the web is allowed and works, so long as you don't...

Unlike `platforms` where you can explicitly overwrite automatic detection, no such thing is supported for wasm. https://dart.dev/tools/pub/pubspec#platforms @kevmoo, @sigurdm this is probably a bit of a hole. wasm isn't really...

Wouldn't it be easier to do source-listings as part of dartdoc generated output? Using github source listings has a few downsides: * People might not be publishing from github. *...

> source listings as part of dartdoc output, and dartdoc already does that. It only does this for exported libraries.. you can't click links and drive into the source of...

Maybe we just need `pub publish` to ask for permission to include a `source` field in the `pubspec.yaml`...

This is blocked by https://github.com/dart-lang/pub-dev/issues/2687.