-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Version 3.0.0-pre is no longer available in npm #820
Comments
|
Some libraries we were depending on (v0.5.0 of https://github.com/jtangelder/sass-loader) relied on it. I can see if they can release a newer version. |
It seems some Sass libraries are having trouble compiling under later releases of 3.0.0-X. If it's not too much trouble, could |
AFAICR, Nonetheless, please pin point where exactly are you having trouble with, we may able to fix it. Because the coming beta and RC will have tons of other breaking changes and these interim builds are meant to change. Moral of the story: don't rely on them too much for serious work unless v3 is solidify. Would be happy to help. |
OK, thanks for the help. My preference would be to upgrade to sass-loader 1.0.0 and use 3.0.0-beta.4. But when compiling Foundation I get this error:
Line 203 looks like:
|
@maspwr I am running into the same thing when I was forced to upgrade this morning, too. I opened an issue, since it's not directly related to this issue. |
@maspwr, do you get the same error with |
Interestingly, yes. But I didn't get it with |
Indeed interesting. AFAICT, we didn't upgraded to libsass v3.2.0-beta.x until node-sass v3.0.0.beta. On this note, can you make an SSCCE for this issue? |
BTW, this error string ("an outer selector from within") was first introduce in libsass v3.2.0-beta.1, sass/libsass#927. Are you sure you are trying with node-sass@alpha? Because at that time we were using libsass v3.1.0. To wit: see https://github.com/sass/node-sass/blob/v3.0.0-alpha.1/package.json#L4 and https://github.com/sass/node-sass/tree/v3.0.0-alpha.1/src (libsassh hash You may need to clean your npm cache. |
I think you are right about the caching issue. Removing |
Note that Foundation has removed that code from partial in their master. You will get exact same error with ruby-sass if you try something like: h2 {
color:transparent;
}
@media print{
h1 {
@extend h2;
}
} |
@am11 We actually just ripped out Foundation, so that issue is no longer a problem. I also haven't seen the compilation hang anymore. We are now running |
👍 |
----- It is inappropriate to include political and offensive content in public code repositories. Public code repositories should be neutral spaces for collaboration and community, free from personal or political views that could alienate or discriminate against others. Political content, especially that which targets or disparages minority groups, can be harmful and divisive. It can make people feel unwelcome and unsafe, and it can create a hostile work environment. Please refrain from adding such content to public code repositories.
Installing version 3.0.0-pre no longer works.
The text was updated successfully, but these errors were encountered: