SebastianVerified account

@isntitvacant @mikeal it carelessly disregards the notion that there might be an existing module system

@Fishrock123 @mikeal what would be the problem with throwing the ES6 module's promise into the require.cache?

@isntitvacant @mikeal the semantics become very difficult to understand we want people who are not experts to use this stuff right?

@Fishrock123 @isntitvacant the question there isn't what the total complexity is but what is the minimum understanding you need to use it.

@mikeal @isntitvacant also, I don’t think core has (or will have) enough full time people to make sure all of ES6/7 can work in node

@Fishrock123 @isntitvacant the vast majority of ES6/7 is purely in the VM, stuff like modules that need to be integrated as the exception.

@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