DefinitelyTyped largely incompatible with ES6 emit due to export syntax

[alexeagle]

DefinitelyTyped is full of the old export = syntax. One random example I ran into:
https://github.com/borisyankov/DefinitelyTyped/blob/master/selenium-webdriver/selenium-webdriver.d.ts#L4847

But when I want to emit ES6, the compiler tells me I need to update that definition file to the new export default syntax. That might be fine for .d.ts files I own, but it's not reasonable to expect all of DefinitelyTyped to be updated by contributors.

I think one of these would be a good fix, in order:

1. Make a commit across all of DefinitelyTyped to update export = to export default. (assuming there is no legacy config where export default doesn't work.)
2. Allow export = syntax all the time, emit the right thing anyway
3. like 2. but using a compiler flag to opt-in

[danquirk]

This is definitely something we've talked about a bunch in relation to the ES6 module changes. In an ideal world we don't break what exists but also help pull people forward to ES6 style modules asap.

[alexeagle]

For now I think my only choice is to fork DefinitelyTyped and fix this in
all the typings I use.

On Mon, Apr 27, 2015 at 11:13 AM Dan Quirk [email protected] wrote:

This is definitely something we've talked about a bunch in relation to the
ES6 module changes. In an ideal world we don't break what exists but also
help pull people forward to ES6 style modules asap.

—
Reply to this email directly or view it on GitHub
#2929 (comment)
.

[mhegazy]

The restriction in the compiler is not needed for ambient modules. we should remove it.

[mhegazy]

handled in #2935

[lazdmx]

👍

[ivogabe]

@mhegazy I think you meant #2935, since #2929 is this issue..

[mhegazy]

@ivogabe yes, you are correct. updating the comment. thanks!