@domenic @lbljeffmo @jumbleofideas @mikeal i even got sick of having to be aware of the cjs -> es module interop in babel that i dont use it
-
-
Replying to @sebmck
@sebmck interesting, I've found it pretty useful@domenic@jumbleofideas@mikeal1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@sebmck (namely -- that I can import any existing node or npm modules)@domenic@jumbleofideas@mikeal1 reply 0 retweets 1 like -
Replying to @lbljeffmo
@lbljeffmo@domenic@jumbleofideas@mikeal i just use `require` and i don't even need to think about it1 reply 0 retweets 2 likes -
Replying to @sebmck
@sebmck what if the npm module is ES?@domenic@jumbleofideas@mikeal1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@sebmck back to the orig topic -- point is that interop is useful *and* has flaws. The two don't have to be mutex@jumbleofideas@mikeal1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@sebmck moreover interop isn't about forever, it's about a means of moving forward to ES modules -- a standard that works native everywhere1 reply 0 retweets 1 like -
Replying to @lbljeffmo
@lbljeffmo you have to break parts of one of them to get that interop though which isn't ideal1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@lbljeffmo you can't compromise es modules because then node will be deviating from the spec and nobody wants that3 replies 0 retweets 0 likes
@lbljeffmo node are definently not going to accept crippling commonjs modules either.
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.
he/him 