I hope this isn't too subjective, but this question definitely doesn't belong on SO...
Here are the methods that I've been researching:
- Include the necessary dependencies in the scripts section for each view when they are needed. (This is what's done in the application's current state, but I believe it's a naive approach)
- Create a giant bundle for all dependancies a la this question (Probably not a good idea, see #3)
- Creating bundles for each combination of dependencies that the views require.
I'm kind of leaning towards option 4, since it appears to meet my non-functional requirements, but to be honest I don't know much about that framework. Additionally, it kind of seems like I lose some of the ASP.NET magic if I go this route such as automatic bundling/minification, which is very helpful during debugging and performance when building for either debug or release. Whereas with option #3 I don't lose those features, but it doesn't seem nearly as manageable in the future.
Is one of these methods significantly better than the others, and/or is there an option that I haven't come across yet that would be even better in this situation?