Mohamed Hegazy (@mhegazy):

If we do not allow --out with --module, then all non-module files (i.e. no top level import/export) should be coerced in a module output. see #2937 for more details.

This has a curious interaction with how ES6 implicitly has modules sometimes, and may require either a breaking change in our parser API or a breaking change in our tsconfig spec or a breaking change in our behavior regarding ES6 and modules. One of them, depending on what we'd rather do. I think that part of this, specifically, should probably be filed as a seperate bug, after looking into it.

Ping Daniel Rosenwasser (@DanielRosenwasser) - I think this is complete as far as this PR is concerned. We'll need to file followup issues regarding implementation of Mohamed Hegazy (@mhegazy)'s change and how it interacts with --target es6.

I would say let's get --module and --out working instead of disallowing it and then allowing it again. it is a breaking change either ways.

as discussed offline, let's close this and support --module and --out combination.