Thank you for this pull request.

Unfortunately, depending on Babel is the very opposite to what "minimalistic" word means. Comparing paulr113/bytenode: "1,744 items (and 11 hidden), totalling 6.7 MB" with OsamaAbbas/bytenode: "5 items, totalling 19.3 kB" is enough for me to refuse depending on Babel and the loads of packages it requires.

You solution can be implemented in another layer, either in a separate project or using webpack (check this plugin).

Thank you again, I really appreciate your effort.

Maybe adding a simplified transform code (e. g. based on Bublé's arrow transform) would be a feasible option here? That would still add a couple dozen kB for the parser but should not be as bad as depending on Babel.

Maybe adding a simplified transform code (e. g. based on Bublé's arrow transform) would be a feasible option here? That would still add a couple dozen kB for the parser but should not be as bad as depending on Babel.

As I said, these solutions can be implemented in another layer. There is no need to be done in bytenode itself. I believe that this narrow focus benefits the project. Also, that arrow issue lies in fact in either Node.js, Electron or v8 (which is more likely), so it should be reported there to get fixed.