@domenic The matching problem is fundamental to the *semantics* of having named/default exports, not the JS syntax.
@domenic The key is that a JS.next import actually represents two things in Node: require + usage. Can require w/o knowledge, but not use
-
-
@wycats Here is the point I am trying to make: https://github.com/wycats/jsmodules/issues/2 … -
@domenic Thanks! The Github issue seems to have fleshed it out. I'll update the website when I get a moment.
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.