js_facade_gen

Bigger difference than that. Flutter has you writing in high-level components that become native draw calls using Skia. There's an in-progress back-end that outputs to HTML, Canvas, and CSS paint instead of Skia. You aren't going to be using npm much at all. https://medium.com/flutter-io/hummingbird-building-flutter-f... If you are using Dart without flutter (eg, overReact), then you're going to use npm a bit more (though dart has better builtin libs which helps a bit on that front). There is a generator that uses typescript definition files to generate dart interopt files. https://github.com/dart-lang/js_facade_gen

> Do you have a good recommended article on that? I don't, but I agree it would be useful. We're not where I wish we were in terms of docs right now. > if Dart requires type bindings (like TS .d.ts files) to the large community of JS projects, how does it plan to solve the kickstart problem. We actually have a tool that will generate the proper Dart interop bindings given a TypeScript .d.ts file: https://github.com/dart-lang/js_facade_gen > It's taken TS community many years to over just the popular js libraries out there. Dart is different from TypeScript in that we are deliberately a more batteries-included system. We wrote and maintain a full set of core libraries (collections, async, etc.) and Google has a well-funded team to ship and maintain a full-featured web framework (AngularDart). So we aren't as stuck needing to rely on the JS