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

Do you need to use sass-3.3.0.rc.1? #50

Closed
ahmednuaman opened this issue Dec 3, 2013 · 2 comments
Closed

Do you need to use sass-3.3.0.rc.1? #50

ahmednuaman opened this issue Dec 3, 2013 · 2 comments
Labels

Comments

@ahmednuaman
Copy link

This version of sass causes the compass gem not to work, sad times :(

@sds
Copy link
Owner

sds commented Dec 3, 2013

Hey @ahmednuaman,

Yes, 3.3.0.rc.1 opened up a bunch of possibilities with its addition of source map support. This gives scss-lint more information about where code was declared without resorting to brittle (and likely incorrect) regex hacks.

Where/how are you using scss-lint such that its dependency on 3.3.0.rc.1 breaks compass? I would think that this would have no effect so long as whatever Gemfile you have declares an explicit version for its sass dependency that isn't the release candidate.

Regardless, the issue you're referring to is still very active, and considering a core contributor of sass is also the creator of compass, I'm sure it will be resolved soon (and yes, scss-lint will upgrade to the latest once it is released).

@ahmednuaman
Copy link
Author

Ok cool, in the mean time I stuck a question on SO to see how I can use scss-lint alongside compass: http://stackoverflow.com/questions/20361074/multiple-versions-of-a-gem/20361417

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

2 participants