-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
@import global path cache "problem?" #265
Comments
The variable |
Hello, Having the same issues as mentioned before. However, next I get an error that $gray-200 is not defined. Trying to run this on fourseven:scss |
I have tried that, sadly it does not work. |
@josensanchez , Any chance you could give me a breakdown of your folder structure? |
nop... if you put everything in the client folder, it would be evaluate following the meteor file load order and the imports would be a mess. I place coreUI inside of the imports directory and in one main.scss on the client directory add the next lines
well, something like that... we organize files differently, but if it's not clear, I'm talking about this file https://github.com/mrholek/CoreUI-React/blob/master/React_Starter/scss/style.scss |
To resolve the issue:
// start of main.scss @import "../imports/ui/scss/core/variables"; @import "../imports/ui/scss/core/typography"; @import "../imports/ui/scss/core/layout"; @import "../imports/ui/scss/custom"; anyone have a better way of doing this? |
This issue happens because the core.scss does not start with '', so it is loaded before the others which start with '', so you get XXX is undefined error |
This is really annoying. I am trying to combine Is there any workaround for this? It makes combining complex sass libraries nearly impossible. |
not entirely sure if its a cache problem, but, importing Core-ui I found several instances of "undefined variable"...
turn out to be that in the bootstrap/bootstrap.scss there is a
@import 'variables';
and after that, in core/core.scss also there is a line with
@import 'variables';
the second one is not evaluated (maybe because is cached from before).
I ended up copying the files to my project and changed this line to
@import './variables';
to search this resource in the same directory and everything works fine (well, repiting the same proccess in the rest of the files).now, they use babel/webpack to transpile their module...
I think it would be nice to first search for @import 'some_resource' in the same directory and then try to get it from the global path, just for compatibility reasons to others compilers in order to be capable to import scss from third party modules
The text was updated successfully, but these errors were encountered: