@trek right, we agree on this. ES6 is not something you should (or even can) deploy (or publish to a registry)
-
-
Replying to @brianleroux
@brianleroux How do you author in es6 modules if you can’t get es6 modules format?1 reply 0 retweets 0 likes -
Replying to @brianleroux
@brianleroux ok, so you’re authoring your app is ES6 (your choice) How do you do `import {foo} from “foo”; and then tree-shake?1 reply 0 retweets 0 likes -
Replying to @brianleroux
@brianleroux how do you not include source you don’t need? Manually find unused fn’s?1 reply 0 retweets 0 likes -
-
Replying to @wycats1 reply 0 retweets 0 likes
-
Replying to @brianleroux
@wycats@trek for serious: is there nothing to be learned here? Interop and small composed builds really so terrible?2 replies 0 retweets 0 likes
Replying to @brianleroux
@brianleroux small modules are great. Making users thing about every single small module they consume: not so much @trek
4:38 PM - 24 Nov 2014
0 replies
0 retweets
0 likes
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.

