It would be good if we built tests, src and dependencies as different chunks when doing a dev build. The reason for this is that when instrumenting with Istanbul via Intern, basically Istanbul ends up instrumenting the whole bundle and collecting data. This causes a significant amount of data to be collected which is then subsequently dropped. Outside of the performance impact in instrumenting and collecting the data, large sets of coverage data can cause issues in certain browsers when posting the data back from a remote session. I suspect any decent sized application would blow up IE11, Safari, and iOS, browsers we have had difficulty collecting coverage data from when they are too large. End users would be clue-less to what the problem is other than staring at their remote session apparently hanging.
Enhancement
It would be good if we built tests, src and dependencies as different chunks when doing a dev build. The reason for this is that when instrumenting with Istanbul via Intern, basically Istanbul ends up instrumenting the whole bundle and collecting data. This causes a significant amount of data to be collected which is then subsequently dropped. Outside of the performance impact in instrumenting and collecting the data, large sets of coverage data can cause issues in certain browsers when posting the data back from a remote session. I suspect any decent sized application would blow up IE11, Safari, and iOS, browsers we have had difficulty collecting coverage data from when they are too large. End users would be clue-less to what the problem is other than staring at their remote session apparently hanging.