[LRUG] resolving JS dependencies on deploy

[Tom Armitage]

I have a Rails project with dependencies on a single external JS library
that for reasons - primarily, licensing - I don’t want to include in my
vendored libraries.

Currently, I’ve been referencing it via Rails-Assets (
https://github.com/rails-assets/rails-assets) which makes it available as a
gem, and thus it’s bundled by the end-user at deployment time.

Except: Rails-Assets is down, again, and the future of the project is
feeling a tad suspect. So I’m asking for myself: what are my alternatives
here?

I am loathe to tear out my basic usage of asset-pipeline to replace it with
some onerous npm-derived asset preprocessing (gulp, grunt, etc, etc, etc);
I also really can’t include the library within my codebase, so need to find
a way for it to be pulled down, both locally (for development) and on
deployment via Capistrano.

Any thoughts? How do you tend to do this?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20151119/354ec6fb/attachment.html>