Closed stouset closed 10 years ago
This is not rails assets issue. Those packages use rails initializers to set custom loading paths.
This means those packages are not correctly packaged for bower.
Please open issue on their repositories, they should use ./bootstrap/something
instead bootstrap/something
in their javascript and scss manifests like this one:
https://github.com/twbs/bootstrap-sass/blob/master/vendor/assets/javascripts/bootstrap.js
depend_on_asset
should also has relative path
Pardon my ignorance, but all of those projects seem to actually point to the https://github.com/twbs/bootstrap-sass/ repo that you recommend as a good example.
@stouset This component is unusable for consuming in bower.
You can use it as native rails gem though:
gem 'bootstrap-sass', '~> 3.1.1'
Shame. You might want to nuke the several rails-assets gems pointing to it, then.
It's up to developer which dependencies he includes, so we don't need to nuke anything ;)
Dependencies of packages are not automatically required.
@sheerun I have to imagine that the SCSS sources for Twitter Bootstrap are a pretty popular use-case for rails-assets. What exactly makes the official sources unusable for consuming with bower, and what steps would be necessary to change that?
They do have a bower.json
; if it's broken somehow, I'm happy to submit a patch and fix it.
I already said it in https://github.com/rails-assets/rails-assets/issues/160#issuecomment-45290361 :)
It's theirs issue, not ours.
The packages
twbs-bootstrap-sass
,bootstrap-sass-twbs
, andbootstrap-sass-official
are broken because they callThese end up being namespaced under the
#{package_name}/
rather thanbootstrap/
or#{package_name}/bootstrap/
, and so cannot be found.