@thomasABoyt Correct, it never made it in.
-
-
Replying to @thomasABoyt
@thomasABoyt Indeed, use `System.define`, or SPDY, etc.2 replies 0 retweets 0 likes -
Replying to @domenic
@domenic@thomasABoyt A use case where module { } would have been useful is writing an ES6-module-aware minifier over concatenated output.4 replies 0 retweets 0 likes -
Replying to @jo_liss
@jo_liss@domenic@thomasABoyt Bundling is a general browser problem (but not a Node problem, e.g.), so solving it in the browser seems +11 reply 0 retweets 4 likes -
Replying to @wycats
@wycats@jo_liss@domenic@thomasaboyt Exactly. Also Loader API does make userland bundling possible, so we'll be able to prollyfill.1 reply 0 retweets 1 like -
Replying to @littlecalculist
@littlecalculist@jo_liss@domenic Here is a picture of the requirements: http://note.io/1fbj5Dm Can you identify where bundling belongs?3 replies 0 retweets 5 likes -
Replying to @wycats
@littlecalculist@jo_liss@domenic Of note: http://note.io/1fbjINg module {} solves it here.1 reply 0 retweets 1 like
@thomasABoyt @littlecalculist @jo_liss @domenic But the real idea is to have a built-in packaging format that can work for all assets w/ URL
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.