import script --> .esm
johnjbarton at google.com
Wed Sep 10 11:14:50 PDT 2014
On Wed, Sep 10, 2014 at 11:02 AM, Guy Bedford <guybedford at gmail.com> wrote:
> On 10 September 2014 19:18, John Barton <johnjbarton at google.com> wrote:
>>> In NodeJS, this can be through `package.json` properties which inform
>>> what module format the package is. In the browser, this could be a header,
>>> or part of package configuration.
>>> John, in your case specifically, it would be good to get more background
>>> to understand what type of meta process is most suitable.
>> What more can I say? Some files need to be parsed as Script and some as
>> Module. Sometimes they are in the same project and sometimes in the same
>> directory. They work on browser and node.
> For Traceur, the default interpretation is as Module, so it sounds like
> you want a way to indicate files which break this rule and need to be
> interpreted as Script?
> Can you give an example of a type of file this would apply to?
Every file in test/ that does not end in module.js (and by extrapolation
every file in every existing test suite based on mocha, jasmine etc).
Every file in src/node/ (and by extrapolation every pre-es6 node file).
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss