I found that simply setting the “publicPath” of the Webpack configuration (there are two of them in devConfig and prodConfig) to a remote server URL does the trick.
All the numbered code chunks (0.js, 1.js, etc.) will then be loaded from that remote URl instead that from “file:///”.
Then it’s just a matter of copying the generated local build directory to the remote server and it works.
If you change something, you have to do a new build and copy the new generated build directory to the server for already distributed App instances to pick up the changes.
I also find, though, that it does not always work…
If you change the HTML, it seems to be no problems, but if a page TypeScript code is changed, it does not work.
Probably main.js bundle inside the App instances is not compatible with the new one and the numbered chunks are loaded, but an error arise.
So this solution seems to work for loading templates from server, but not modules code, so it is not a complete and robust solution…