fix bundle-config-loader

[farfromrefug]

This PR fixes a big issue which appeared with N 7 / esm / webpack

With webpack import / require order is not respected : webpack/webpack#1343

Now in bundle-config-loader we rely on require to load bundle-entry-points thus calling initGlobals and making tslib functions global.
Because it uses require it actually end up at the end of your main.js (simply look at a generated bundle.js)

To keep that call up we need to use import
But that is not enough!
in bundle-entry-points we use 'require' on 'globals'. And using import is not enough either because we call a method on it which will end up after all imports!

The solution to all this is call initGlobal inside global/index.ts then use import './global' for example.
Doing that i needed cleanup a bit and we end up with only on use of initGlobal

EDIT: that app will crash on ios because of that. The reason is that i import View at the top of my main.ts which include files using __metadata

[NathanWalker]

Thank you @farfromrefug !

[farfromrefug]

@NathanWalker can you guys test this on your side before we publish this?
Like with real apps

[farfromrefug]

Actually already released:) hope it won't break somewhere:)

[farfromrefug]

@NathanWalker what happened here? That PR seems messed up. DOes not link to my branch anymore master...Akylas:bundle-entry-points

And the issue is still here #8872

[NathanWalker]

The PR you had done here was from a branch on master called bundle-entry-points (wasn't created from your fork):

[farfromrefug]

@NathanWalker sorry misread ! But wait why is it my description if not my PR? What s going on here?