SebastianVerified account

@sebmck what if the npm module is ES? @domenic @jumbleofideas @mikeal

@sebmck back to the orig topic -- point is that interop is useful *and* has flaws. The two don't have to be mutex @jumbleofideas @mikeal

@sebmck moreover interop isn't about forever, it's about a means of moving forward to ES modules -- a standard that works native everywhere

@lbljeffmo you have to break parts of one of them to get that interop though which isn't ideal

@sebmck definitely not ideal. But in many cases the parts you have to trade-off are acceptable. Globally ideal wouldn't be a productive goal

@lbljeffmo you can't compromise es modules because then node will be deviating from the spec and nobody wants that

@sebmck I see at least 1 or 2 viable paths forward that don't compromise ES modules or any existing CJS modules

@sebmck it compromises some interop cases -- but not any existing CJS, not any newly minted ES going