Asp.Net MVC 5 has the concept of creating resource bundles which reduces the number of resources the browser has to pull down, and the size of the resource. I'm not aware to what extent that MVC goes through to remove code that is never called, but this process works pretty well.
Having used all three solutions I'm aware of some tradeoffs:
- Resource Bundles are easy to set up and integrate. They just lack the mapping file to make debugging easy.
- Webpack has a high learning curve, but is capable of doing some very impressive things. If you intend on using React, it's almost a necessity. If you have a UI that is talking to a REST API layer, it's the way to go.
The short answer is, you are probably going to get the most bang for your buck by using resource bundles in your particular case.