Yes, you're right. But at the same time, I don't think Lyo is to blame here.
First, I don't understand the node.js delay to support standard module (esm is 3k stars on github). Then, I don't understand Browserify refusal to support them (like webpack do).
Devs should pressure both of those to align with w3c standards and get rid of this CJS/AMD/UMD/Export crzyness.
I think Lyo is a tool that need to die (as good as it is), but in the mean time it's good to have it.
Coding is as much a matter of personal growth as it is of logic and control-flow. I keep patience, curiosity, & exuberance in the same toolbox as vim and git.
*Opinions posted are my own*
Yes, you're right. But at the same time, I don't think Lyo is to blame here.
First, I don't understand the node.js delay to support standard module (esm is 3k stars on github). Then, I don't understand Browserify refusal to support them (like webpack do).
Devs should pressure both of those to align with w3c standards and get rid of this CJS/AMD/UMD/Export crzyness.
I think Lyo is a tool that need to die (as good as it is), but in the mean time it's good to have it.
I like that. "A tool that needs to die". Very cool.