Kevin Moore

There are three classes of package: * `host-app` \- the source application. Do NOT include the actual app package name. * `private-pkg` \- a non-public/published package. Do NOT include the...

https://github.com/dart-lang/web/actions/runs/20084884864/job/57620047495?pr=487 It'd be awesome if there was more information here. Not sure if this is an SDK thing or a pkg:test thing

Make it easy to use type B in place of type A when there is an obvious/explicit conversion from B -> A

3

Every place in `pkg:http` with a `url` parameter types it as `dynamic`. ```dart Future get(url, {Map headers}) => ... void doWork() async { await get('http://example.com'); await get(Uri.parse('http://example.com')); await get(42); //...

pkg:listen – hopefully

3

Assuming things get approved, excited to go here! See also: https://github.com/flutter/flutter/pull/171055 https://github.com/dart-lang/core/pull/898

### What information needs to be added? https://dart.dev/interop/js-interop/package-web#conditional-imports https://dart.dev/tools/pub/create-packages#conditionally-importing-and-exporting-library-files We duplicate content here. We should document exactly which `dart:` libraries apply to which platforms/compilers (JS, Wasm, Native) We should have...

Now that this package has been migrated to `pkg:web` we should validate it works with dart2wasm Blocked by https://github.com/dart-lang/test/issues/2143

Need to investigate!

See https://github.com/dart-lang/tools/actions/runs/19683968169/job/56384815965#step:5:16

When publishing a breaking change version, give me warnings about public API marked @deprecated

5

When publishing a new breaking version (v1.x.y -> v2.0.0) – this is the time to remove cruft. The pub client can checked to see if the version I'm publishing is...