proposal: `legacy_js_interop`
legacy_js_interop
Description
Warn on all usage of "legacy" JS-interop features that are not compatible w/ dart2wasm
Details
See https://github.com/dart-lang/sdk/issues/50665
Will need to pull in @srujzs or similar for all details
Kind
Guards against errors when targeting dart2wasm
Bad Examples
TBD – using dart:js features, dart:html
Good Examples
Using new JS interop features TBD
Discussion
See https://github.com/dart-lang/sdk/issues/50665
"legacy" JS-interop features that are not compatible w/ dart2wasm
What features are these?
@mnordine – we're not quite ready to enumerate them. We're hoping to have a story outlined by end-of-January
@kevmoo I think js_bindings is a good way to avoid dart:js and dart:html.
Please, tell us if you need us to change anything in the lib to make it comp to this new wasm/js standard.
An alternative, but a bit stricter, proposal: https://github.com/dart-lang/sdk/issues/54347