SebastianVerified account

@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"

@lbljeffmo i guess there's ways you can import cjs into es but you can't go the other way which is what people want too

@sebmck I can imagine interop in both directions. ES -> CJS: Live bindings + toplevel await convert to live properties/System.import()