SebastianVerified account

@Fishrock123 @isntitvacant if modules specifically are too complicated to ensure compat then we have the option of not supporting it.

@mikeal @Fishrock123 @isntitvacant Modules are not complicated. People trying to make require work on ES6/import on CJS are complicating

@domenic @mikeal @fishrock123 @isntitvacant commonjs interop for es modules is just a massive rabbithole of problems

@sebmck @domenic @Fishrock123 @isntitvacant which is to say interop with 99% of the JS modules in existence is a rabbithole of problems.

@mikeal @domenic @fishrock123 @isntitvacant yes. there's no solution where you aren't making massive compromises.

@mikeal @domenic @fishrock123 @isntitvacant if you want commonjs then use `require`, if you want es then use `import`. why is that bad?

@sebmck @mikeal @domenic @fishrock123 @isntitvacant what happens when you don’t know what the module is? i.e., something from npm?

@sebmck @mikeal @domenic @fishrock123 @isntitvacant unless it’s something like: npm -> use require(), your code -> use `import`