Running "sass:dist" (sass) task
Warning: bower_components/foundation/scss/foundation/functions:13: error: error reading >values after )
Use --force to continue.
Aborted due to warnings.
Look below for solution.
So I found the solution to the error thanks to:
Michael Degli-Angeli
(9/11/2014) - It appears Micheal removed his post from the following link/thread
http://foundation.zurb.com/forum/posts/19063-grunt---error-error-reading-values-after----libsass
Turns out this is a error with Foundation and just started happening today. (9/10/2014)
The Solution:
Just remove !global from line 13 in
bower_components/foundation/scss/foundation/_functions.scss
and run grunt like so:
./node_modules/grunt-cli/bin/grunt
Note: Be careful if your bower.json is compiling with the latest Foundation.
The problem when removing !global is that I have now a very long compiled output file with a lot of dupped stuff. Just use the inspector in Chrome and you'll see... I can't find other solution for now...
Simply updating grunt-sass seems to do the trick, see Paul Angus's reply on Zurb's forum
npm install --save-dev grunt-sass
Afterwards, grunt build should compile with no errors.
Related
I've been trying to get Sass up and running with Bootstrap. I've followed the tutorial, going so far as to install exact versions of the dependencies listed rather than the default/latest versions. I've done this from scratch at least three times. I've uninstalled and reinstalled different versions of Sass and Compass (mainly according to Sass --compass --watch Error: Cannot load compass), as well as older versions of Ruby (I just installed 2.3.3, down from the latest release).
But whenever I get to running the grunt sass command, something goes wrong. I've gotten errors about not being able to load Compass. If I search and rectify that, I'll go through an error or two more (not on hand sorry, I've closed everything out), but keep ending up on:
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/compass-core-1.1.0.alpha.3/lib/compass/core/caniuse.rb:72: warning: circular argument reference - browsers
NoMethodError:  
Use --trace for backtrace.
Warning: Exited with error code 1 Use --force to continue.
I've looked up this error, and I've tried doing the bundle update listed here, but end up right back where I started with the same problems (since now there are updated versions of dependencies that apparently don't play well together, and compass things don't work again).
I know how to use Sass, I just can't practice since I can't get it running. I'm newer to coding, and I don't know Ruby at all, so I'm stuck now that my search-fu has failed me. My machine is running Windows 10. I am specifically looking to set up Sass to run with Bootstrap 4 (yes, I know it's in alpha, it's what I'm required to use for work) and there doesn't seem to be any good documentation out there about how to actually get it running properly.
When I use lessc to compile a less file, in the output CSS i always get as first line of the file this string:
(node) util.print is deprecated. Use console.log instead.
I googled the error but I don't understand if this is due to a nodejs error or a lessc one.
I tried also to run lessc -s but it didn't solve my issue.
Any idea how to fix it?
Typescript compilation task works fine on linux machines but on a mac fails with the following not particularly useful error message and what looks like a binary dump.
$ grunt
Running "ts:build" (ts) task
Compiling...
Fast compile will not work when --out is specified. Ignoring fast compilation
Using tsc v1.4.1
������������=��AF���=����
>> Error: tsc return code: 3
Warning: Task "ts:build" failed. Use --force to continue.
Aborted due to warnings.
Im using nvm with node v0.11.4 and rvm with ruby v2.2.0.
Any ideas how to fix this, or even debug?
As the question includes debugging, here are some pointers which might help determine where the problem is.
Try compiling from the command line with tsc alone (no grunt), in case the problem is with grunt or the ts:build task (looks like grunt-ts).
Maybe one of your source files is causing the tools to crash (perhaps they can't cope with a file's encoding?). If a single, simple file will compile, then try removing subsets of your source from the build. If some of those files are causing the crash (whether valid TypeScript or not) you may be able to find a temporary workaround.
Try compiling with different versions of tsc. If you need 1.4.1 features you could try using the latest from https://github.com/Microsoft/TypeScript (see here for how to do this with grunt-ts).
The problem was with a malfunctioning node installation. I upgraded to node 0.12 which fixed the problem.
Just to check the problem wasn't node 0.11.4 specific I removed all previous versions of node and reinstalled 0.11.4 and the error no longer occurs.
I took these steps after removing all node modules, clearing the cache and reinstalling with no luck. I also tried using multiple typescript compiler versions.
I'm working to try to install the boilerplate-bootstrap example in a effort to learn/play around with assemble. The example fails for me after I try to run grunt saying to please run bower install before continuing. Looking in the Gruntfile.js, I can see that it is looking for vendor/bootstrap/_config.yml. Seems like I'm doing something pretty basic wrong here. the example I'm referring to is listed here:
https://github.com/assemble/boilerplate-bootstrap
Let me know if you have any suggestions at all for me - thanks
Just follow the prompt and run bower install bootstrap. All will make sense afterwards. The _config.yml file is in the root of the Bootstrap project, but you won't find it unless Bootstrap is downloaded with Bower first.
I'm trying to create a sprite with compass, but I keep getting this error:
NoMethodError on line ["225"] of /Library/Ruby/Gems/2.0.0/gems/chunky_png-1.2.7/lib/chunky_png/canvas/png_encoding.rb: undefined method `downto' for 150.25:Float
I have tried everything including using previous version of chunky_png and reinstalling compass and sass.
Would love to know how to fix this.
Thanks
I found the solution. I just had to update all of my ruby gems and then restart my computer. I have had no problems since.