I’m using reasonML and js_of_ocaml; it’s a large codebase and I’d really like to be able to see (at least some approximation of) the line number in the reason code where an error is thrown in the browser developer console. The current behavior is that it just attributes the error to a line in the compiled javascript.
I’ve been playing with compiler flags; combinations of {–debuginfo, --noinline, --sourcemap}. These seem to result in reasonable-looking attribution in the js source, but I’m not sure if I have to do something else to expose said attribution in the dev console?