Using twitter-bootstrap-rails without Bundler.require01 Feb 2013
Myron Marston recently wrote a post recommending the removal of Bundler.require. Go read his post. Go ahead. I’ll wait.
I didn’t find anybody on Google with my same problem, so I’m documenting it here for posterity. (And to partly remind my future self how much of a dumb Rails noob I was when I wrote this post).
disables part of Rails’ autoloading mechanism. Which means your asset
gems don’t get autoloaded, which means you get all sorts of weird errors
in your application log, like so:
ActionView::Template::Error ('twitter/bootstrap/bootstrap.less' wasn't found. (in /Users/matt/Code/my_test_app/app/assets/stylesheets/bootstrap_and_overrides.css.less)):
And then you pull your hair out googling, and searching on stack overflow for the solution, because surely, in the 2 months since Myron’s post was published, somebody has run into this, right? RIGHT? No, they haven’t, or they’re smarter than me and figured it out on their own.
What the hell do I do now?
I spent what I thought was an exorbitant amount of time trying to figure out why this wasn’t working, what was actually going on, and how to fix it.
The first clue is just before the conclusion of Myron’s post:
Many gems provide rake tasks. If the gem is no longer being loaded at environment boot time, these tasks may not be available. Ripple, for example, provides a handful of rake tasks. To make these tasks available in your application, you’ll need to add load “ripple/railties/ripple.rake” to your Rakefile, which is essentially what the rake_tasks block in Ripple’s railtie does.
The second clue came when I was looking in
is where the
require statements for a bunch of railties live.
The solution is actually really simple. Add
require "less/rails/railstie" require "twitter-bootstrap-rails"
config/application.rb and suddenly the error about not behind able
to find that bootstrap.less file I mentioned above just disappears.
But wait, there’s more!
I ended up getting a similar error with jQuery.
Ok, we’ve been here before. This is simple now. Add
config/application.rb and now I am greeted by the empty view I put
in place for my default route.