The thing with the double download is very specific to IE11 and that one Safari version, that one safari version can be fixed with a script (standard included in the webpack-module-nomodule-plugin) but the one from IE11 seems a whole lot different. I do think that with the deprecation of IE11 coming up soon'ish we shouldn't worry about it that much but rather provide compatability to legacy and reward people using modern browsers with a quicker loading path.
That's my two cents on the matter, ofcourse we could also search for a second compat script to prevent double download.
To be honest, I should just test it with deferring the nomodule but haven't come to that yet.
This is a good point. It's definitely a good technique to shrink bundle size and that's likely worth it alone.
I'll have a play around with it myself.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.