Syntax Error in _maps.scss in Susy 2.0 - susy-compass

"Syntax error: Invalid CSS after \"...th($_keys, $_n)\": expected \")\", was \": $_value);\"
on line 57 of *myPath*/sass/lib/susy/math/_maps.scss
from line 4 of *myPath*/sass/lib/susy/_math.scss
from line 4 of *myPath*/sass/lib/susy/language/_susy.scss
from line 4 of *myPath*/sass/lib/_susy.scss
from line 4 of *myPath*/sass/screen.scss"
I am getting this syntax error when trying to use the new Susy 2 with Compass. I wanted to upgrade from version 1 manually and copied the contents of the downloaded sass folder into my sass/lib. Therefore, I do the import with #import "lib/_susy";.
Anyone knows if this is my fault or a bug?

Had these problems as well. To fix, I had to:
Upgrade to Sass 3.3 RC5 (gem install sass -v 3.3.0.rc.5)
Upgrade to Compass 1.0.0.alpha.18 (gem install compass -v 1.0.0.alpha.18)
This should fix it for you, too.
Edit: Sass 3.3 has now officially been released, so you can install the production version. Compass 1 is still in prerelease.

Related

php spreadsheets Parse error: syntax error, unexpected '.', expecting '&' or variable (T_VARIABLE)

I have installed phpspreadsheets with composer using command line(back to medieval era..). Now, I have some errors after I have included the phpspreadsheets library in my project:
Parse error: syntax error, unexpected '.', expecting '&' or variable (T_VARIABLE) in ..../application/libraries/vendor/phpoffice/phpspreadsheet/src/PhpSpreadsheet/Calculation/Engine/Logger.php on line 93
So, in Logger.php on line 93 the code is:
public function writeDebugLog(...$args)
Has anyone dealt with such issue ? it's so annoying, it took forever to install composer and run install stpreadsheets from command line and now this error...(and the fact that I have to use command line it's killing me)
The library you installed probably depends on 5.6 or newer and you probably have an older version. The ... operator was added in PHP 5.6 so if you are on an older version it should be a syntax error. See PHP.net for docs.

Error: Module version mismatch. Expected 47, got 48

I'm writing a Visual Studio Code extension which uses a native node.js module. When I try to debug this extension in vscode I get the error message from above, when loading the native module (when commenting out the require() call no error comes up). It tried quite a few steps to overcome + test this:
npm uninstall native-module followed by a npm install native-module --save-dev in my vscode extension folder, this compiled the native module completely and without problems.
Completely cleaned my node_modules folder in the extension and did again the npm install --save-dev.
Installed node.js again, both LTS and current. With LTS the error message changes to: expected 47, got 46.
Installed latest vscode (August recovery build)
Launched a node session in my vscode extension folder and loaded my native module. This works nicely.
Read the various questions and comments here on SO. They mostly recommend what I described above.
Still, I cannot get vscode to accept my native module. What can I do? From the above steps it appears as if vscode has been built with a node.js version between current and LTS. Can I force my native module somehow to use a specific version?
Btw. what do those numbers 48, 47, 46 etc. actually mean? The node.js version is of course in the typical form: major.minor.build and nothing of that matches the above version numbers.
Update:
ok, I found what those numbers mean: https://nodejs.org/en/download/releases/
Once you know what those numbers in the error message mean it's easy to solve the issue. Simply install the node.js version that is expected. In my case it's node.js 5.12.0.
Remove node_modules folder
Run npm update
Then;
Run npm install

Functions may not be defined within control directives or other mixins

In my nodeJS project suddenly it give error.I do not any upgrade or changes.
When I write NPM start in command line it give that error
ERROR in ./~/css-loader?sourceMap!./~/postcss-loader!./~/sass-loader?
sourceMap&outputStyle=expanded&includePaths[]=c:/TFS/rc1/app/scss&includePaths[]
=c:/TFS/rc1/~/compass-mixins/lib&sourceMap&sourceMapContents=true!./app/scss/_toolkit.scss
Module build failed:
undefined
^
Functions may not be defined within control directives or other mixins.
in c:\TFS\rc1\node_modules\compass-mixins\lib\compass\functions\_lists.scss (line 81, column 3)
# ./app/scss/_toolkit.scss 4:14-337
I reinstall compass-mixins package but it still give same error.Then I looked _lists.scss that file in 81 line there is a code .I deleted that bu it give same error.What should I do?
#if not(function-exists(compact)) {
#function compact($vars...) {
$list: ();
#each $var in $vars {
#if $var {
$list: append($list, $var, comma);
}
}
#return $list;
}
}
I also face the similar problem. And my project is using gulp-sass and compass-mixins. As heart.cooks.mind points out that, gulp-sass is depending on node-sass. And node-sass upgrade one of its dependence libsass to version libsass 3.3.3 Delorean since node-sass 3.5.1.
However, one of libsass 3.3.3 Delorean changes is related to this problem:
'Disallow functions to be defined in control directives or mixins (#mgreter, #1550)'
Obviously, _lists.scss in compass-mixins break this rule. Seems someone raise an issue to compass-mixins and they have idea on fixing it.
Before compass-mixins release the issue fixed version, my temporary workaround is to delete node_modules/node-sass manually and npm install node-sass#3.4.2
I had the same issue,please refer to node sass release 3.5.3 is breaking build and force lock gulp-sass to use the specific node sass library using shrinkwrap and avoid using the buggy version of node sass
I am using Gulp. Version 2.3.0 of gulp-sass breaks it. Go back to Version 2.2.0 and you are all fixed.
Edit:
The real culprit is the node module inside the "gulp-sass" node module known as "node-sass". You can see inside "gulp-sass"'s package.json file that it simply pulling version greater than ^3.5.3.
Even if you go back and reinstall "gulp-sass" to 2.2.0, as I suggested earlier, the package.json file in there will still pull "node-sass" greater than ^3.5.3.
If I use the older version of "node-sass" 3.4.2 that error goes away. I don't know how to fix that in an automated way. In a pinch I was able to fix the problem by copying that folder (that is using 3.4.2) from a different project that works. Now it compiles.
Can someone smarter than me figure out a better way to accomplish this result?
What I (temporarily) did, was to install globally the node-sass v3.4.2, and then replace the gulp-sass version of node-sass (it is located within gulp-sass/node_modules) with this older one.
sudo npm install -g node-sass#3.4.2;
sudo cp -r /usr/lib/node_modules/node-sass/ /usr/lib/node_modules/gulp-sass/node_modules/;
Btw, there is a PR waiting to be merged for this. But if you want to use this today then there's a fork of the merge too.
If you want to use latter then just put compass-mixins: tjenkinson/compass-mixins in your package.json and all will be good.
Update:- There's also an npm package for the latter mentioned in the PR now
Update 2:- This should no longer be a problem with v0.12.8 now

"Error: Failed to locate couchnode native binding" on nodejs file

"Error: Failed to locate couchnode native binding" i get this error when i try to run an express.js file on my terminal. I found here an answer for this problem. (https://stackoverflow.com/questions/26451470/trouble-configuring-building-couchnode-on-ubuntu)
I did this in the .gyp file and everything went well. But after a day something broke into my node_modules and i the following error again. I changed again the .gyp file then made again the npm rebuild but nothing changed. I still getting this error. Anyone can give me other solution ?
I ran into the same issue. If you open //node_modules/couchbase/builderror.log file, there is a line that looks for python version "python -V.." and it clearly said that python version SHOULD be > 2.5 and < 3.0
I uninstalled the python 3.4 which was there and installed 2.7.9, then "rm node_modules" --> npm install and voila, no more errors.
Hope this helps.
Cheers!

Error using Compass 1.0alpha, Sass 3.3, and Susy 2.1.2

I used Fire.app before but they haven't updated for a long time.
Then I turn to Compass 1.0.0alpha, Sass 3.3, and Susy 2.1.2
I installed via gem:
compass (1.0.0.alpha.19)
compass-core (1.0.0.alpha.19)
compass-import-once (1.0.4)
sass (3.3.8)
susy (2.1.2)
While creating a new project using susy:
compass create --using susy,
an error reads:
error sass/style.scss (Line 4 of sass/_grids.scss: File to import not found or unreadable: susy.
Load paths:
/******/sass
/Library/Ruby/Gems/2.0.0/gems/compass-core-1.0.0.alpha.19/stylesheets
Compass::SpriteImporter)
Many articles say a 1.0alpha version of compass will do, but it appears not.
How do I solve the problem? Thanks!
I don't know where SpriteImporter figures in your website. However, I would suggest installing Bundler, creating a Gemfile to include at least these two:
gem "susy", "~>2.1.0"
gem "sass", "~>3.3.0"
Then let Bundle install all the gems required. In case you aren't aware, this will be done inside Terminal on mac. The Bundler website explains all.

Resources