@mikesherov @brianleroux There are already two parsing goals (FunctionBody for CJS modules and Script for everything else)
@bradleymeck @mikesherov @brianleroux not true of <script type=module>, TypeScript or Babel. Not true of Ember CLI.
-
-
@wycats@mikesherov@brianleroux Node is CJS, browser <script> is Script, <script type=module> is Module. only compile to one/UMD -
@wycats@mikesherov@brianleroux an example is using babel for CJS from ES; loaded as CJS in node. Interop is more than compile targets -
@wycats@mikesherov@brianleroux we don't really have an existing host env that supports 2 native level module systems yet -
@bradleymeck@mikesherov@brianleroux ember-cli w/ ember-browserify is one such environment. 1/ -
@bradleymeck@mikesherov@brianleroux Right now we use import 'npm:*' due to the primacy of standard modules, but working to eliminate 2/2 -
@wycats@mikesherov@brianleroux this looks like it is just transforming the source down to Script if I am reading it right? -
@bradleymeck@wycats@mikesherov waking up to this thread.
Time to reboot the spec for sure! NBD. Happens. -
@brianleroux@wycats@mikesherov Problem was TC39 said "we know best", didn't invite others in.@bradleymeck and@jrburke should have been. - 8 more replies
New conversation -
-
-
@bradleymeck@mikesherov@brianleroux ember-browserify (https://github.com/ef4/ember-browserify …) is pretty popular. People are trying lots of things. -
@bradleymeck@mikesherov@brianleroux configuration is usually involved somewhere to mix and match. depends on primacy of CJS vs. standard -
@wycats@mikesherov@brianleroux CJS is what is currently used in node and npm. bigger to me than ES to avoid breakage of the existing stuff -
@wycats@mikesherov@brianleroux ES is high, even trying to keep .js is, but < backwards compatibility and not breaking ecosystem/tools
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.