Yeah well, thanks for bringing figures on that @bfv, this show up quite clearly the impact of angular for launch time. On top of that, adding a full set of node modules and a consequent app is a real pain.
Regarding to emulators, it's right, there is visible impact on performances, and you cannot relie on it to juge to the performances. I would say it's the case for any app (even native), but for this particular purpose, it's a very tricky thing.
Then, a little bit of feedback about implementing webpack on an existing project :
firstname.lastname@example.org, our first move was to make a fresh project and doing the exact same thing.
This went well for us withtout any issue, and the difference is significant event for a clear project (the default app template launches at least twice as fast on a Nexus 5X).
Then, the pain started.
Removing all the requires for a quite big project is very long. Yet not very complex for much cases, we had to update all our dependancies for which fortunately the last versions embedded a correct
main value in their
I have to note that the
telerik-ui stuff was the most tricky thing import correctly.
The webpack compiler throwed a very strange error because we did not have a
main.aot.ts file (No mention of that in the documentation).
globals.addModule trick to use require is not that easy to work with, we had the chance to use only well typed packages to avoid using it. (After we took 3 hours replacing all the requires with it )
We finally managed to build the project with webpack, abd its reaaaaly a fresh breath !
We still need to fix some issues with custom shema imports, but it's drastically more efficient.
To sum it up, I can't figure out why webpack is not defaultly embedded by the nativescript CLI. The work is almost done here ! For all the new projects that are comming up, it's not an issue to make correct imports, I've not seen much of other drawbacks using webpack.
Now, your move