Currently the output from webpack for the client side mapping code is quite large (2-3MB on production mode). This is expected as its a large application, but this generates warning in webpack and could be better optimised by either reducing the bundle size further, or by using splitting behaviour.
At the time this was a low priority and a single 2-3MB js file was considered good enough, but this could be improved.
The warnings are turned off in the webpack.prod.js.
Currently the output from webpack for the client side mapping code is quite large (2-3MB on production mode). This is expected as its a large application, but this generates warning in webpack and could be better optimised by either reducing the bundle size further, or by using splitting behaviour.
At the time this was a low priority and a single 2-3MB js file was considered good enough, but this could be improved.
The warnings are turned off in the webpack.prod.js.