Rudi Grinberg

Oh I see. I didn't read the PR implementation. I thought you meant producing the final `.js` from the `.cmo.js` files while completely side-stepping `.cma`. I see that you're just...

> It's actually more complicated for dune as you need to be able to deal with arbitrary compiler version. How come? Wouldn't this knowledge come from ocamlep?

I think you have the right idea. We require a tighter set of constraints for packages to be buildable by dune. The upside of that is that we offer a...

I don't see the issue with adding more aliases (what's the downside?), but in your example you can already execute your tests individually by building the expected target. E.g. `dune...

Okay, then the command should be `dune build example.output` or whatever. You just need to build the target that is produced by your command and doesn't live in the source...

Okay, that's convincing. Feel free to send a PR to add an alias

Yes, it should be possible

We could generate a shell script that does the equivalent of `OCAMLRUNPARAM=b exec ...`, but that would be problematic on windows. A better workaround to turn on backtraces would be...

We already impact your performance in the development profile to improve user experience.

This was discussed in the last team meeting. The consensus was that the benefits outweigh the cons and that having the backtraces on is the better default, especially for newcomers....