Not sure if this is something to be posted here or the webpack issues...

Environment
Created a brand new test app today; latest of everything..

• CLI: 5.4
• Cross-platform modules: 5.4
• Android Runtime: 5.4
• iOS Runtime: 5.4
• Plugin(s): (none extra)
• Webpack 0.22

Describe the bug
If you set "useLegacyWorkflow": false everything works great
If you set "useLegacyWorkflow": true most of the app is broken...

To Reproduce
Happens on both iOS and Android.
You can download my repo from: https://github.com/NathanaelA/event-order and build with Webpack disabled; and you should see something like this when you click the "Navigate" button.

JS: ----------------------------------
JS: Starting navigation to aa-page
JS: aa-Page actually loaded and parsed by JavaScript Engine
JS: NavigatingFrom main-page
JS: NavigatingTo aa-page
JS: loaded aa-page
JS: layoutChanged aa-page
JS: unloaded main-page
JS: NavigatedFrom main-page
JS: NavigatedTo aa-page

Delete your platforms, delete app off of phone/emulator, disable LegacyMode and try it again and you will see this:

----------------------------------
JS: Starting navigation to aa-page
JS: NavigatingFrom main-page
JS: unloaded main-page
JS: NavigatedFrom main-page

First of all you will see NONE of the aa-page events are wired up. AND on the AA-page; the navigate button is disabled (so it also didn't wire up).

Please note Android is easier to test than iOS as I don't have a close button (yet) on the showmodal call; the ShowModal button is also likewise broken..

Expected behavior
Things to work in a Webpacked app. 😀

Sample project
https://github.com/NathanaelA/event-order