Current ES6 module syntax

Question

Please can someone confirm that the following syntax is still valid in ES6?

module "javascripts/bar" {
    export function Bar() {}
}

I am thinking about the scenario where I use concatenation. Yes I know HTTP2 will make concatenation moot, but I would like to concatenate my modules today.

If this is not valid, how should I construct my modules so that they remain valid in the same file?

It cannot be parsed by esprima, or transpiled by 6to5, so probably not. — Felix Kling
– Felix Kling, Commented Dec 15, 2014 at 18:09
Similarly, module is not on the latest list of keywords. (It'd be nice if the spec were actually readable, though, eh? I thought the ES5 spec was bad, but it's got nothing on the ES6 spec...) — T.J. Crowder
– T.J. Crowder, Commented Dec 15, 2014 at 18:13
@Felix is there a forum where I can ask detailed ES6 questions other than S/O? — Ben Aston
– Ben Aston, Commented Dec 15, 2014 at 18:13

Benjamin Gruenbaum · Accepted Answer · 2014-12-15 19:01:40Z

4

This is the old module syntax that was removed. The above is no longer valid since Rev28 of the ES6 draft. Do not use this syntax any more it is not valid ES6. (relevant esdiscuss with it being removed) (esdiscuss coming to the conclusion to remove it)

ES6 has a module-per-file module. If a file is imported using import it will be treated as a module.

Update: I just noticed that Alex has written about it that is probably a good read on the subject. His links are wrong though.

edited Dec 15, 2014 at 19:01

answered Dec 15, 2014 at 18:47

Benjamin Gruenbaum

278k90 gold badges524 silver badges524 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Current ES6 module syntax

1 Answer 1

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Linked

Related