Philippe Elsass

Oh do you mean there are 2 Modular apps loaded in one page? This won't work right now - there is no scoping of the global brigde...

Hmm wait. It should work to have 2 libs, or at least you can make it work by making sure the code in the `libs2.js` adds libraries to the global...

The libs template here https://github.com/elsassph/haxe-modular/blob/master/doc/npm-setup.md should allow multiple libs.js to add to the registry.

Oooh. Ok my bad, so the pattern in the doc is indeed wrong. The solution would be to "add" the libraries references into the existing `__registry__` instead of replacing the...

But it would be better to always resolve this global registry instead of keeping a reference to the first one found.

@peteshand you're right, this looks like I did a mistake here.

Modular supports node - either through Webpack with the Haxe loader, or using `-lib modular -lib hxnodejs`. I'll need to think about the Typescript definitions question... It will be problematic...

`hxtsdgen` should work with Modular, that is the non-Webpack splitting. I don't believe it can work with the Webpack Haxe Loader, because Haxe compilation happens dynamically when Webpack "loads" `hxml`s....

Er... would a `.hxml.d.ts` be picked by Typescript? This is something I didn't consider...

Is it the `-js` output?