SebastianVerified account

@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

@sebmck forward, and with viable workaround for new deps from CJS -> ES

@sebmck happy to discuss in non-Twitter about specifics if you have specifics you think can't be mitigated

@lbljeffmo parsing as script vs module is the biggest thing

@sebmck yea, def has trade-offs. I think import/export presence is a pretty viable trade-off. There will be implicit-strict mistakes

@sebmck made, just like if one had to opt in to modules another way and forgot to specify "is module"