Asset Loader Library

I don't understand what problem this library tries to solve. How hard is it to load assets? Why would I want to depend on an external library and learn how to use it for a task as simple as loading assets?

Valid question. A lot of people put all their assets together and minify them so they can load them in a single call on every page, in which case this library probably isn't applicable. The problems I originally was solving in my first version of this:

1. The need to load specific styles and scripts for certain pages, not others
2. The need to use a single header/footer template that could somehow have assets "injected" into them
3. The need for cache resets on assets updates (using timestamped parameter suffixes)

After numerous iterations of the original CI3 library I settled on the directory structure version because it made it easier for me to control which files were loaded while not trying to "track" them anywhere else (though the $routes variable offers this additional functionality).
Thanks for the question! Would you share how you handle assets?