thank you for your reply.
I find the CRG rather inconvenient - presently I can update a line in my packages.json and get a new version, which is then copied to the wwwroot/lib through a gruntfile.
Say that most of my pages only use an autocomplete, a dropdown and a toast, then I'd like to render a partial view that includes exactly those scripts and css.
Another page may then load a bigger component, such as the Schedule, where again I may have included a dropdown and an autocomplete as well.
On that page, I may want to render a different partial to only load those components.
Using the CRG, I'd have to re-do this for any combinations of files that may be required, and also lose the option of caching individual file that may have been in use before. So a user who visited page one will already have requested the js file for autocompletes and dropdowns before, those would be in his cache.
I am very interested in your suggestion number 2; to either use webpack or require.js or similar methods to leverage the Async module loading that appears to be available.
Thank you very much!