-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Make @import Paths Relative #112
Comments
You are supposed to copy the contents of the https://github.com/JohnAlbin/normalize-scss/tree/master/fork-versions/typey-chroma-kss into your Sass folder. It sounds like you have a |
Yes, for a number of reasons I chose to copy the normalize-scss (typey-chroma-kss) directly in my repo project: I've edited:
... and it works fine. I think that these changes would also work if normalize.scss was installed, or placed in the Sass folder, this being the reason why I proposed to change the paths to relative paths. |
Thanks for the reply. I'll consider this for the next point release. |
I'm using normalize-scss (typey-chroma-kss fork) in a project. I didn't install the lib, just copied the relative sass folders into my project.
When I built the project I get error imports with a few files — for example in
normalize-scss/base/grouping/_grouping.scss
... because normalize-scss is not on Sass Load Paths.
I've solved it by adding normalize-scss' path to the
SASS_PATH
environment variable — on Windows:And of course, it could be set via Sass command line options too.
I think that changing the dependencies
@import
paths to relative paths would be a better solution:... this would allow normalize-scss to work out of the box without having to set Sass Load Paths; and it shouldn't create any problems for those who installed normalize-scss via NPM, Ruby Gem, etc.
It's just a small issue, for which there is an easy solution, but — unless preserving dependencies import paths the wat they currently are is really necessary — it would make its out-of-the-box use neater and simpler, and also avoid any potential clashes with other similar named modules on Sass Load Paths.
The text was updated successfully, but these errors were encountered: