Support non-esm modules

[kapouer]

The simplicity of it is so cool. It's a proof-of-concept however - i'm a noobie w.r.t. acorn.

[marijnh]

Did github mangle the (code.charAt(ast.start) == "" ? "" : "") expressions or is there something I don't understand going on there?

[kapouer]

Not github, me - to be able to diff i removed semicolons too agressively.

[kapouer]

That should fix it

[kapouer]

I don't expect these PR to be accepted right away - please consider them as inspiration, if that's not too much to ask :)

[marijnh]

What do you want to do with require calls?

[kapouer]

Nothing: most front-end modules come in a single require-able bundle, so exporting module.exports using that patch, es6-style, is just enough to be able to import the npm-installed bundled module.

[kapouer]

Though replacing require x by import from x would be elegant but i fear the hidden complexities.

[marijnh]

most front-end modules come in a single require-able bundle

In my experience the concept of dependencies is definitely also used in many front-end modules. So shipping a solution that just ignores that doesn't feel very reasonable. (I intentionally didn't provide any support for non-ES modules initially because I'm not that interested in being pulled into the morass of trying to make this work.)