From: es-discuss [mailto:[email protected]] On Behalf Of Mark Volkmann
> Can we say anything more concrete if we restrict the discussion to modern > browsers as opposed to non-browser ES engines? Is it fair to say that in > those environments a file will always be treated as a module if it is > imported by another file that the browser has loaded? Concretely, the plan of record (which may change as implementation realities descend upon us) is: - Any code inside `<script type="module">` will be parsed as a module - Any code inside `<module>` will be parsed as a module, if we can get away with the relevant parser change - Any code which is imported, e.g. via an `import` statement inside another module, or via a `System.import` call in a script or module, will be parsed as a module That basically leaves any code inside of or loaded by a non-`type="module"` `<script>` as script code, with all others module code. +Dave to correct me if I got any of this wrong. _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
