-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sass::SyntaxError: File to import not found or unreadable: bootstrap. #315
Comments
I witnessed this happen during a workshop. It doesn't seem to happen on all platforms. It may be specific to Windows. |
Is this only on JRuby on windows? Can we recreate it on linux / mac? |
Hi, haven't seen it on linux. Seems to be a windows only thing. |
Hrm. Okay, I don't have a windows box (old 98 VM though) to test with. On Thu, Jul 25, 2013 at 10:39 PM, Markus Eisele notifications@github.com
|
Ok, I have to clarify this a bit. The error happens during startup of the development server with awestruct -d Here is a complete output with --verbose flag:
|
What does the _ext/pipeline.rb look like after generation? On Mon, Jul 29, 2013 at 6:04 AM, Markus Eisele notifications@github.comwrote:
Jason Porter |
Here we go :) Awestruct::Extensions::Pipeline.new do extension Awestruct::Extensions::Posts.new '/news'extension Awestruct::Extensions::Indexifier.newIndexifier must come before Atomizerextension Awestruct::Extensions::Atomizer.new :posts, '/feed.atom'end |
Looks to me like what you're missing is
At the top of that pipeline. In |
Jason, I wonder if the substitution that is performed during the site creation is
It's either the fact that the file is being opened twice or that the unlink
I'm almost certain this is the issue. -Dan On Tue, Jul 30, 2013 at 11:14 AM, Jason Porter notifications@github.comwrote:
Dan Allen | http://google.com/profiles/dan.j.allen |
I'm working on getting a complimentary Azure account dedicated for the -Dan On Thu, Jul 25, 2013 at 10:41 PM, Jason Porter notifications@github.comwrote:
Dan Allen | http://google.com/profiles/dan.j.allen |
Yes we do. This would be very welcome. On Tue, Jul 30, 2013 at 6:28 PM, Dan Allen notifications@github.com
|
@LightGuard you're right. Adding that "require" Statement is working. I actually missed that part which is kind of annoying. The only feedback I can give is, that this is a usability issue. I am (mostly) aware of the fact that you reduced the required dependencies with making more stuff optional but the error message is not really helpful and even worse: The development server actually includes the relevant css to the generated sources. Thanks for looking into it anyway,
|
In version 0.5.3 this is taken care of, the require statement is On Tue, Jul 30, 2013 at 10:05 PM, Markus Eisele notifications@github.comwrote:
Jason Porter |
Markus, to clarify the script is supposed to be adding this line but for By design, it's supposed to just work. We'll make sure it does ;) |
Thanks! And sorry for the trouble! |
No trouble at all. In fact, thank you for reporting it! Btw, this is still open. I may have discovered the issue, but we haven't yet applied the fix and verified it. |
Also a little bit of formatting.
Using -i -f bootstrap leads to a
ERROR: Failed to render: /stylesheets/styles.scss
Sass::SyntaxError: File to import not found or unreadable: bootstrap.
Load paths:
on Windows ...
The resulting css does include the styles ...
/* line 19, ../../../../jruby-1.7.4/lib/ruby/gems/shared/gems/bootstrap-sass-2.3.2.0/vendor/assets/stylesheets/bootstrap/_reset.scss */
The text was updated successfully, but these errors were encountered: