Typescript: Conditionalize `__esModule` emit?
Numerous issues pointed to from https://github.com/microsoft/TypeScript/pull/32083 have people running in environments where it's not safe to emit the __esModule property for whatever reason.
Instead of adding a flag, we could just emit (typeof exports !== 'undefined') && Object.defineProperty(...
Thoughts?
RyanCavanaugh
All 3 comments
one use case for this is, if you use Typescript to generate mongodb atlas stitch code, it won't deploy, unless you manually remove the Object.defineProperty(exports, "__esModule", { value: true }); at the top.
the reason is simple, it expects always one exports = () => {} per file at the top, additional functions on the same file may come at the bottom of the function. so, that conditional check won't help in this case, you should be able to completely suppress that helper function (someone mentioned Closure Compiler, the scenario is alike)
pocesar
on 23 Oct 2019
Any updates? Almost one year since this issue was created.
kirchet
on 5 Apr 2020
Hi, I also ran into the same problem...
andrascii
on 5 Apr 2020
Related issues
manekinekko
路
3Comments
bgrieder
路
3Comments
seanzer
路
3Comments
remojansen
路
3Comments
dlaberge
路
3Comments
Most helpful comment
one use case for this is, if you use Typescript to generate mongodb atlas stitch code, it won't deploy, unless you manually remove the
Object.defineProperty(exports, "__esModule", { value: true });at the top.the reason is simple, it expects always one
exports = () => {}per file at the top, additional functions on the same file may come at the bottom of the function. so, that conditional check won't help in this case, you should be able to completely suppress that helper function (someone mentioned Closure Compiler, the scenario is alike)