[MGatner]

Along the same lines as this, the second library is published! Check out the user alerts library announcement: https://forum.codeigniter.com/thread-73096.html
While publishing that one I realized I hadn't tagged tatter/assets with a release so composer was giving warnings unless you changed your minimum stability. That's fixed now so the asset loader can correctly be installed: `composer require tatter/assets`

[MGatner]

Small update, thanks @PaulD, the library functions now return their output instead of displaying them directly. This shouldn't be a big change since there are no views in use, but the helper functions now should be output instead of simply called:
`css();` -> `echo css();`

[MGatner]

Version 2! Not really a big change but I moved configuration from the constructor to a Config file and replaced the helper with an actual Service. This change will break existing uses of the library, but version 2.0 should prevent Composer from auto-updating it. If anyone does update from 1 => 2 just be sure to save any custom configs (app/Config/Assets.php) and port them into a new config file using Assets.php.example as a base.
Check out the third library if you haven't already: Traffic Tracking (https://forum.codeigniter.com/thread-73161.html)

[MGatner]

Hi all- Sorry for so many iterations here, but this was one of the first modules I tackled when I was still learning CI4. I'm sure there's a lot more room to grow, but I've come a long way with CI4 and modules and finally refactored Assets to take advantage of some of these. Check out the release notes for more details:

https://github.com/tattersoftware/codeig...s/tag/v2.1

Of note, Assets now includes publishing from manifest files. This should make it a lot easier for developers who use package managers (like Composer) to maintain links between the package versions and the published versions.