Closed glebm closed 7 years ago
Looking now.
Looks like popper.js doesn't really support bower:
It seems like the maintainer of that project isn't really interested in supporting bower, which is his choice, but unfortunately since there is no bower metadata in the project's repository, there's nothing we can do here.
Thank you! Do you know if there is a bundler-to-yarn/npm proxy?
I'm afraid not. However, you can use these natively with Rails 5.1:
Well I'm packaging Bootstrap 4 for Sprockets so I need a gem. I've solved the problem by packaging popper.js as a rubygem: https://github.com/glebm/popper_js-rubygem
We really would like to implement bundler-to-yarn/npm, as you say, in Rails Assets. PRs welcome. Poke me if this is something you (or anyone else!) would like to work on.
Need list, es5?
Can you elaborate?
How could a bower metadata file help you? I'm not against Bower per se, I'm against the idea to put compiled code in the repository.
If the idea is to simply add a bower.json file I'm okay with it.
Unfortunately it's really an issue of putting compiled code in the repository. I understand why you're against it, but rails-assets.org can't work without it since Bower's file format doesn't give any hints as to how to build the code in the first place 😄
¯\_(ツ)_/¯
@glebm your best bet is probably to fork it, compile it, commit it, and point Rails Assets at your fork.
I'm open to PRs to introduce some kind of automatic magic that pushes the compiled stuff in a different branch on each release. Always if Bower allows to define a branch different from master
...
For some reason, the
rails-assets-popper.js
https://github.com/FezVrasta/popper.js, does not have thedist/
directory.It is a dependency of the current Bootstrap 4 master, so it'd be nice if it worked.