How to find a bug that only happens in the Javascript version of a Dart program?


I’ve written a program that runs perfectly in Dart but fails to run in the transpiled Javascript version. I suspect it’s an infinite loop (because CPU usage goes up). Has anybody experienced such a behavior before? Maybe even more important, how can I find out the problem?


Dart can generate source maps since a while which makes it quite easy to debug generated JS.
With source maps the browsers show Dart code and stack traces when debugging built JS code.

Source maps need to be enabled in the browser (see for details) and in the $dart2js transformer (see for details)

Answered By – Günter Zöchbauer

Answer Checked By – Jay B. (FlutterFixes Admin)

Leave a Reply

Your email address will not be published. Required fields are marked *