detecting JS language mode for tools

John Barton johnjbarton at google.com
Fri Jan 24 09:55:00 PST 2014


If we are asking questions: why two parse goals? Why not allow import in
Script and let it act like the code was wrapped in Loader.import() and
allow export then just ignore it?  The semantics of 'var' would be changed
by appearance of 'import' just like the semantics of code changes with the
appearance of 'use strict'.


On Fri, Jan 24, 2014 at 9:32 AM, David Bruant <bruant.d at gmail.com> wrote:

>  Le 24/01/2014 18:26, John Lenz a écrit :
>
>
>
>>  REPL is a dilemma: if you parse as module, then obtaining the last
>> expression value is not simple. if you parse as a script, then common
>> cut/paste fails on export/import statements.
>>
>
>  My basic question remains.  As a tool owner how do I know if what I'm
> looking at is intended to be a Module or a Script?
>
> How do you know if some code is intended for the browser or Node?
> How do you know some code is intended to be used in a WebWorker and not in
> the main thread?
> How do you know the code won't be concatenated a "use strict" when someone
> else uses it?
>
> The code itself lacks the context in which it's being loaded (hence very
> defensive patterns like UMD (Universal Module Definition)).
> If you want to be exhaustive, you'll have to make an assumption or make
> your tool smarter about the context.
>
> David
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140124/9dd20ba5/attachment.html>


More information about the es-discuss mailing list