Skip to content
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 #113

Closed
wmantegna opened this issue Jan 6, 2016 · 10 comments
Closed

Sass::SyntaxError #113

wmantegna opened this issue Jan 6, 2016 · 10 comments
Labels

Comments

@wmantegna
Copy link

I'm building a Ruby on Rails application that uses the sass-rails gem for pre-compiling.

I have tried every combination of the following file naming conventions & files where the include-media file is imported:

  • _include-media.scss, include-media.scss, include-media.scss.css
  • home.css.scss, application.css.scss

As soon as I add the following line of code to a .css.scss file:

@import "include-media";

Regardless of the combination used, I get the following error:

Sass::SyntaxError at /
Invalid CSS after "  'phone'": expected ")", was ": 320px,"
(in .../app/assets/stylesheets/application.css.scss:35)

Which seems to be caused by line 35 of the include-media.scss file.

@KittyGiraudel
Copy link
Collaborator

Which version of Sass are you using?

@wmantegna
Copy link
Author

gemfile specifies: 'sass-rails', '~> 4.0.2'
terminal says I have versions 5.0.4, 5.0.3, 4.0.5, 4.0.2 installed

I've changed the gemfile to specify for 5.0.4 and still experienced this issue.

@KittyGiraudel
Copy link
Collaborator

I suspect you are using Sass 3.2 under the hood, which would explain the issue.

@wmantegna
Copy link
Author

What version of Sass do I need?

@KittyGiraudel
Copy link
Collaborator

3.3+. :)

@wmantegna
Copy link
Author

Looks like sass-rails doesn't support 3.3 yet. I tried swapping out sass-rails for the 'sass' gem (using sass v3.4), and ran into this error:

Sass::SyntaxError at /
File to import not found or unreadable: scaffolds.

Is there a way around this? Or am I stuck waiting for sass-rails' next release?

@KittyGiraudel
Copy link
Collaborator

The latest error you had is unrelated to include-media, and I believe comes from the fact you try to import an unknown file.

@noelchavez
Copy link

Hi had same issue updated my sass -v from 3.2.19 to 3.4.20 still getting an error.

@KittyGiraudel
Copy link
Collaborator

Is this still an issue? I cannot (and have never been able to) reproduce it on SassMeister.

@KittyGiraudel
Copy link
Collaborator

I’m closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants