Closed erikdahlstrand closed 12 years ago
Whoa, that's not good. What does your top level asset manifest (maybe application.css) or sub asset file (maybe foo.less.css) look like?
I have application.css.less .
//= require twitter/bootstrap
//= require_self
#my-styles { }
I get this error message also with a completely empty css file (without require twitter/bootstrap).
This is one reason I wanted to get the combustion project in for testing this engine and making sure it all work. Will do that for this fix.
FYI, but I won't be able to get to this for a while, so if someone makes a pull request before I do, I'll take it.
I've figured that out and it is a strange combination of a few different things. First I've had to change the path that is added to the app.config.less.path
array to: 'vendor/assets/stylesheets/twitter'
in engine.rb (I've included that in a pull request regarding Rails 3.1.1 initializer grouping).
But I also had to change something in less-rails which is the dirtiest hack I've done in a long time, so I won't send a pull request for that but maybe it helps people to get going in the meantime: You've to open the template_handlers.rb file of the less-rails gem and copy the whole LessTemplate class to a new class named Tilt::LessTemplate. So that you practically overwriting the original LessTemplate class of the Tilt gem. The normal precompilation process didn't use the provided class, even as it is added as an engine in the railtie.rb. Don't know why, though :/
Hope this helps a little to get up to speed again.
@walski Awesome Thorben!
Gonna close this out and deal with it under ticket #7
FYI, should be solved by using the latest less-rails, less-rails-bootstrap and rails 3.1.1 But please test and let me know under that ticket #7
Hi,
Can you precompile the assets? In a vanilla app with empty stylesheets (just less-rails-bootstrap in my Gemfile) I get...