-
Notifications
You must be signed in to change notification settings - Fork 34
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
Including paths from a file #52
Comments
Having the same problem. I need to define one npm script entry for each SCSS file I need to compile, to avoid node-sass-chokidar to import also include files, like: I have something like:
By default, node-sass-chokidar reads all the directories recursively and tries to compile each file, regardless of being just an import from other file. |
Same issue here as well. I think it would be nice if it can support a wildcard like |
Trying to add import-glob-loader2 to it might help with the wild-card import. |
UPDATE!: (Solution): Used: https://www.npmjs.com/package/node-sass-glob-importer
Can now use: in my scss files. |
I'm for even just making the CL statement shorter like |
This is a feature request. Including multiple paths in the script really becomes uncomfortable. For example:
This can longer and longer. It happens because some libraries import their dependencies using absolute path. For example: foundation-sites provides a _settings.scss file which can be imported if I want to override basic stuffs like color, width, height etc. However, in that file some dependencies are imported like parent/module. So it throws an error.
So, my request is to introduce a way to include paths from a file (ex. .chokidarrc) in the node-sass-chokidar processing. Thus multiple paths can be easily included in the file without any hassle.
Note: Please, feel free to suggest me alternatives.
The text was updated successfully, but these errors were encountered: