The ES* modules vs CJS modules thing shows that TC39 got it wrong. Time to get back to the drawing board and have a look at the cowpaths.
-
-
Replying to @brianleroux
@brianleroux How do you keep the goodness of static module declarations but also hold onto CJS? There's a big cowpath around import now too.1 reply 0 retweets 0 likes -
Replying to @davemethvin
@davemethvin sorry I can't hear you over the sound of my shipping code in production that uses no static module declarations1 reply 1 retweet 8 likes -
Replying to @brianleroux
@brianleroux@davemethvin 95% of CJS declars are statically analyzable. You can build a rollup/tree-shaking for CJS. It's just a bit harder2 replies 1 retweet 3 likes -
Replying to @amasad
@amasad@brianleroux It's a LOT harder unless you declare parts of the language off limits. const x = require("x"); ... x[method](42);2 replies 0 retweets 0 likes
@davemethvin looks analyzable enough; perhaps not as optimizable as you'd like, but that's something different @amasad @brianleroux
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.