he/him 
@Fishrock123 @mikeal what would be the problem with throwing the ES6 module's promise into the require.cache?
-
@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 This answer, seriously. -
@jumbleofideas@sebmck@mikeal@domenic@fishrock123 If you're using ES modules, then you can't use any existing `require`-based modules? - 32 more replies
New conversation -
-
-
@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` - 8 more replies
New conversation -
-
-
@sebmck@mikeal@domenic@Fishrock123@isntitvacant you can’t import in a non-ES6 module. require(‘es6’) and import from ‘cjs’ must work.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.