I'm currently working with singularity.gs v1.7.0 and I noticed that the helper files _box-sizing.scss, and _clearfix.scss, are not included into the _helpers.scss file. I did had the same experience with singularity.gs v1.6.2.
Here is how I'm including singularity.gs into my SASS code and also how I'm going around this issue:
#import "_singularitygs.scss";
// for some reason the content bellow wasn't called from inside singularity
#import "singularitygs/helpers/_box-sizing.scss";
#import "singularitygs/helpers/_clearfix.scss";
// end of missing libraries
Can somebody confirm if this is a bug or not, and what would be the preferable procedure to including these two files?
Unfortunately I wasn't able to find a clear answer on the documentation.
Thank you
Related
For example, a lot of the SASS I have been writing require and use the mixins from bootstrap. However, I would like everything to not be complied into one large file. So for example in a main.scss I could have:
#import 'bootstrap/assets/stylesheets/_bootstrap';
#import '_mypage'
#import '_mypage2'
but when you compile the file it would just end up as one file where I am trying to get it so I have bootstrap, mypage, and mypag2 as separate css file, while maintain the ability to use the bootstrap.
Is there a way to do this in sass? Or should I be looking at certain tools to achieve this goal?
IIRC, the _ in front of SCSS files is what tells the compiler not to make its own file. What you're telling the compiler with your #import lines is that you want all of those files to be added to the top of your main.scss.
If you make a mypage.scss, and put it in the same directory where the compiler is looking, it will compile to its own file. You can either import bootstrap at the top of that file as well, or just load earlier it in your HTML to be able to reference it.
LESS CSS has got the feature where one can include a LESS file by reference. Is this or something similar possible via SASS through the #import directive?
This question already has answers here:
Can I import an externally hosted file with sass?
(6 answers)
Closed 6 years ago.
I am trying to import the variables file into a sub-project. I want to have a single variables file, which would give theme to the both main and sub-project.
Hence, I am importing the variables file by using the full path in my sub-project, like :
#import "http://main-project-url/scss/_variables.scss";
OR
#import url("http://main-project-url/scss/_variables.scss ");
However, I am getting errors while accessing those variables declared in _variables.scss file.
Can someone help me, please..!
Thanks in advance!
SuryaPavan
Because #import is overloaded in SASS, it's hard to tell but just because it compiles does not mean that the variables in .scss are getting interpreted.
You might look at remote-sass which purports to do what you ask:
RemoteSass is a small gem that allows Sass to import remote sass/scss
stylsheets over HTTP/S. With this, you can set up a central server to
serve your stylesheet assets and share css among your many
applications.
I have this folders structure:
~/css/file1.less
~/css/folder/file2.less
What I want to do is importing file1.less inside file2.less, so in my file2.less I have this code:
#import "../file1.less";
This do not work, and the compiler crash when I build the project.
I execute the compiler in Visual Studio 2010.
How can I import a less file placed in a parent folder?
You must prepend ./ to your path. For example :
#import "./../style.less"; /* Correct */
#import "../style.less"; /* Wrong */
This seems to be a bug in LESS.
Comments in the bug report suggests that it is fixed in the main branch, so if you get the latest version from git, maybe it will work.
See https://github.com/cloudhead/less.js/issues/177 and this post on StackOverflow: Node.js + Express.js. How to RENDER less css?
I just tested importing a file which is one level up the way you did it and it works for me.. What's the compiler's error on crash? The error may help you.
On a sidenote, you should probably keep your .less files structured differently.
Try this:
#import "~/root_css_folder/parentfolder/file1.less";
When trying to make a Cocoa framework I ran into the old problem of the headers not copying, which I fixed by changing the visibility(?) of the headers to public. now I Would Like to organise the framework more logically. when the headers are copied there are are placed all in the same directory with no subfolders. I would like it to organise the framework by placing the headers in sub folders so that I can #import them like:
#import <Myframework/Math/MathFunction.h> // import some math related functions
however I notice that the system frameworks contain subframeworks. If I must I am willing to do that and also is there a fast way to convert all the
#import "someFile.h"
to
#import <Myframework/somefile.h>
in the release so the in other project I can #import them without confufing the compiler?