Followed the instructions to download the sass Foundation version. (http://foundation.zurb.com/docs/sass.html)
I keep getting the following error in app.css
Syntax error: File to import not found or unreadable: foundation/_functions.
Load path: /Users/xxx/Desktop/sandbox/app
on line 13 of scss/_settings.scss
from line 1 of ./scss/app.scss
Any ideas?
Inside of the foundation folder there should be a file named _functions. The underscore in front of the name indicates that it's a partial file and is compiled into app.css using #import.
1: Check to see if _functions is in the foundation folder
2: If it is, check your import path
3: If it's not, try downloading Foundation again
Just as a tip, I like to use a app called Mixture.io. In addition to having a lots of its own features, it makes setting up a Foundation project a cinch.
Hope this helps.
Related
i want to install ruby website on my machine but i have this probleme hwo can help me
I am having an issue trying to import SCSS files in my Nativescript app. I am adding these lines to add my default theme styles in my app, the lines are added in the app.android.scss and app.ios.scss:
#import '~/assets/skin';
#import '~/assets/list';
The files are inside app/assets folder and their real names are: _skin.scss and _list.scss.
The problem is when I try to use Nativescript Sidekick and build for iOS in the cloud it gives me this error:
Found peer node-sass
[17-10-25 13:55:16.820] (Info) Error: It's not clear which file to import for '#import \"assets/skin\"'.
[17-10-25 13:55:16.822] (Info) Candidates:
[17-10-25 13:55:16.823] (Info) assets/_skin.scss
[17-10-25 13:55:16.825] (Info) assets/skin.css
But building the app for android locally it works.
Any suggestion?
Thanks!
I'm following this example for using Flask-JWT:
https://pythonhosted.org/Flask-JWT/
And I get this error when I start uwsgi:
Traceback (most recent call last):
File "./wsgi.py", line 1, in
from main import app as application
File "./main.py", line 5, in
from auth import api_auth
File "./auth.py", line 3, in
from flask_jwt import JWT
File "/opt/mist_base/env/lib/python2.6/site-packages/flask_jwt/__init__.py", line 83
for claim in verify_claims
^
SyntaxError: invalid syntax
I've been only using Python v2.6.6 (for Centos 6.x per customer specification) for only a week so I'm still very green at it. As a result, earlier today I discovered I had multiple variations of JWT-something in my virtualenv so I removed all instances and only reinstalled Flask-JWT. I had thought the issue was library conflicts (and it may have been earlier), but I'm still getting this error and other people have used it with no issues. Am I doing something wrong or is this library simply not designed to be used with Python v2.6.x?
[UPDATE] I've gone ahead and compiled v2.7.12 from source in CentOS 6 and so far it works nicely for my needs. I found these directions:
http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/
and was able to install in an alternate directory.
This library just doesn't work on Python 2.6. The source code relies on features like dict comprehensions that only exist in 2.7 and up.
I am trying to compile my Sass file, but keep getting this error in my terminal:
error sass/app.scss (Line 60: File to import not found or unreadable:
custom.
This happened after:
cd to the containing folder
sass --watch `sass:css`
What did I do wrong? What steps should I take? Do I need to use Compass to use Sass?
Using the new Yeoman beta 1.0
I bootstrapped an angular application, and installed foundation via bower.
When I run my server, I get this error:
error app/styles/main.scss (Line 7 of app/components/foundation/scss/foundation.scss: File to import not found or unreadable: modular-scale.
The import is #import "modular-scale";
I tried to change that to #import "foundation/functions/modular-scale";
But got a loop warning then, saying it was trying to import itself.
Tried adding the ruby gem 'modular-scale' in my grunt file, under compass with
require: 'modular-scale'
But it doesn't seem to work either
Anyways, I am not sure what to do here.
I had a similar problem when migrating an app to 1.0. Bower was installing the components into a top-level components directory instead of at app/components. If that is the case, one fix is to add a file .bowerrc with
{
"directory": "app/components"
}
I'm not sure the root cause, as creating a new webapp with Yeoman 1.0 doesn't suffer from this problem.