Add OMIT_MODULE_EXPORTS to omit module code

[kjlubick]

This export code is the root cause of flutter/flutter#58428 so we would like to be able to remove it.

[welcome]

Thank you for submitting a pull request! If this is your first PR, make sure to add yourself to AUTHORS.

[sbc100]

I would love to find a way to do this without adding a new settings if we can. However, I'm not familiar enough with MODULARIZE or the its users. Maybe there are other options such as completely removing the UMD style export stuff?

Does the EXPORT_ES6 mode also cause you problems?

If we are going to add a new option I think we need a better name because both MODULE and EXPORT are pretty overloaded here. Maybe something more specific like NO_UMD_EXPORTS?

@RReverser has been battling with modularize recently so might have some insight into the right direction to go here.

[kjlubick]

ES6 modules do work for the browser, but they make use on node.js more problematic (unless we want multiple builds, one for node, one for web).

I'm fine with renaming the option to NO_UMD_EXPORTS so as not to be confusing with the Module object.

[kripken]

@kjlubick For your use case, can you build with EXPORT_ES6 (which would avoid emitting UMD code)?

[kripken]

Oh sorry, I just saw the last comment now. So ES6 modules don't work in node. Is there no way to ignore them there, or is it a syntax error?

[kjlubick]

AFAIK, there is no way to ignore the export command in node.js

[RReverser]

Looking at flutter/flutter#58428, it seems that your issue is rather that it's an anonymous define?

I thought these should work fine with Require.js, but, if not, maybe a better fix would be for us to generate some name there?

[RReverser]

So ES6 modules don't work in node. Is there no way to ignore them there, or is it a syntax error?

Wait, ES6 modules do work in Node nowadays, and few versions ago got even unflagged. Can you try with latest Node.js version and set Emscripten's output extension to .mjs (which implies EXPORT_ES6)?