es6->es5 transpile
stagas opened this issue · comments
a few things to consider:
- is it worth it? it'll introduce too many issues, for stuff that will eventually be supported natively in the browsers
- in-browser transpile will generate too much garbage, might be killing the live performance, maybe have a backend service and post es6 code, get es5 back?
- we already have code with es6 style import/export so maybe a regex replace solution to commonjs require/exports?
- this needs to be addressed before #5
we can add a dummy async indirection for now that will eventually be replaced with a transpile/fetch modules step.