Downloadable compiled packages separately?

[bronius]

I am looking at the difference between this repo (thank you for maintaining!) and original:
https://github.com/jjj/chosen/releases/
https://github.com/harvesthq/chosen/releases/

and see that this one contains compiled assets under ./docs. I don't know how to extract only that file or how to move that folder into my preferred destination project libraries folder using composer for the Drupal chosen module, so instead I modified where Drupal looks for its assets (by tacking on docs/).

Ok this works, but it's not ideal, and I wonder if I can try something different or if there is something on your end that could be done differently to alleviate this one little workaround (ie. provide compiled assets as a separate download here in the repo or if there is some composer config to extract just what I need and discard source).

Thanks!
-Bronius

[JJJ]

Hey @bronius! In those situations, I've just been manually including the compiled assets into the project without using Composer. It's obviously a little more work though.

We could include a build directory, which would be kept up-to-date manually by me basically, until something better comes along anyways. What do you think?

[bronius]

Happy new year! Thanks for your reply :)
Well, don't bend over backwards for me -- but consider why this library exists (I presume as a replacement for harvest), and how I came to it (seeking a drop-in replacement for an outdated harvest version). To serve that need, yes, a build folder would be so fantastic! I have no idea what it requires to maintain such a thing: extra cycles? something built-in to github but costs something? .. no idea :)