couldn't find file 'bootstrap/glyphicons-halflings-regular.eot'

[irobayna]

I am using bowerify and bower-rails gems, setup per the instructions on config\application.rb

config.bower_components_path = Rails.root.join('lib/assets/bower_components')

also on application.css.scsss

...
*= require bootstrap-sass-official/vendor/assets/stylesheets/bootstrap

and I am getting the following error:
sprockets::FileNotFound

couldn't find file 'bootstrap/glyphicons-halflings-regular.eot'

Any ideas what could be wrong?

[kaievns]

hey Isi, thank you for reporting the problem. would it be possible for you to make a simple dummy rails app that reproduces the issue so I could debug it and make it work? Thanks.

[astjohn]

I've just run into a similar issue with the chosen.js library. To reproduce, make a rails app, add bower, and add chosen. Note I have added config.assets.prefix = '/assets_dev'

Here's what I have found while digging:

The location of the file in my source is:

/Users/astjohn/Development/appie/rails_app/vendor/assets/components/chosen/chosen-sprite.png

However, upon requesting the resource, the error I'm given is:

ActionController::RoutingError (No route matches [GET] "/assets_dev/chosen-sprite.png"):

When I run rake assets:precompile the image chosen relies on is written to

/Users/astjohn/Development/appie/rails_app/public/assets_dev/chosen/chosen-sprite-0e1e2418c607b6511764ace58a19b657.png

So it looks like the subfolder named chosen under my assets folder is creating a problem since the request expects it to be at the root of the assets folder.

Any ideas?

[astjohn]

Guess I might have jumped the gun. I switched from the pre-minified css file to the minified one.

The main difference that I can tell is that the css was url(chosen-sprite.png) in the non-working, minified one and url('chosen-sprite.png') in the working css file.

Once I switched, I was presented with a Rails error though:

ActionView::Template::Error (Asset filtered out and will not be served: add `Rails.application.config.assets.precompile += %w( chosen/chosen-sprite@2x.png )` to `config/initializers/assets.rb` and restart your server

Once I did that, all was fine, but with the newest version of sprockets and rails 4, this all seemed redundant. In fact, I didn't need bowerify at all. However, adding that stuff to assets.rb seems like a pain.

Anyway, hope this helps others.

[kaievns]

hey adam, it seems that the unquoted urls are not parsed out correctly, i'll see if i can fix that. as for the Rails.application.config.assets.precompile += %w( chosen/chosen-sprite@2x.png ) part that's crashing, i understand that's your code. technically it shouldn't be there, bowrify should add all the bower assets automatically.

Also, not sure what do you mean by the new sprockets did they fix the issue with relative assets urls?

[astjohn]

Hi Nikolay,

I have no idea. I'm a bit late to jump onto the rails 4.x upgrade and I'm still sorting through everything. All I know is that I have sprockets 2.12.3 and rails 4.1.8. In my application.rb, I have
config.assets.paths << Rails.root.join('vendor', 'assets', 'components')

Then, while I was following along with the upgrade, I created an initializer that looks something like:

# Be sure to restart your server when you modify this file.
# Version of your assets, change this if you want to expire all your assets.
Rails.application.config.assets.version = '1.0'
# Precompile additional assets.
# application.js, application.css, and all non-JS/CSS in app/assets folder are already added.

Rails.application.config.assets.precompile += %w( management.js management.css partner.js 
                                  highlight.pack.js highlight.css
                                  i18n/en.js i18n/es.js i18n/fr.js)



# Bower component images and such
Rails.application.config.assets.precompile += %w( chosen/chosen-sprite.png chosen/chosen-sprite@2x.png)

Then I removed bowerify and everything still worked. Either way, bowerify is great so thank you for your effort with it! One of the reasons I didn't jump on the other bower gem was I felt like there was too much overhead. This gem solves that problem and lets you just plug in bower. I guess I'm a minimalist. Glad I could help track down that parsing issue.

[kaievns]

I see. My guess is that the chosen package has the asset images being referenced correctly, so by just adding the images to the precompilation list you made it work. That's cool.

Bowerify does pretty much the same thing under the hood, it's pretty minimal, it adds the assets to the recompilation list. Although it also resolves issues with some packages having their assets referenced via relative paths in their css, like url("../img/stuff.png") assets pipeline still doesn't fix that as far as i know.

[kaievns]

Hey Adam, could you show me how you included the chosen package into your application.sass file? I'm trying to reproduce the issue, and i only see a sass file in the bower package for chosen, which kinda makes sense why it works for you, because images are referenced via the assets pipeline image-url helper

[astjohn]

Sure. In my bower.json, I have:

"chosen": "https://github.com/harvesthq/chosen/releases/download/v1.2.0/chosen_v1.2.0.zip",

That gives me a folder structure under vendor/assets/components/chosen/ which contains a bunch of files, but the main ones are chosen.css, chosen.jquery, etc. The images I was referring to are also under this folder. This non-standard way of referencing that zip file was taken from their docs.

I reference the required files in the asset pipeline the usual way: *= require chosen/chosen.css

Hope that helps?