You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
module.paths is a predefined variable containing all the node_modules search paths to find installed packages. It returns already an array in the current form:
// Generate Source Maps if the source-map plugin is present
It only checks for strings rather than for a path array. Is it safe to submit a PR for this change, or is there any reason more technical reason behind the check for the string story?
Happy to contribute this small adjustment.
The text was updated successfully, but these errors were encountered:
It only checks for strings rather than for a path array.
There must be something else going wrong with your setup, because arrays are perfectly supported.
The code snippet above first checks if opts.includePaths property is set/non-empty. If the value is not set or is empty, the code makes sure that it is an (empty) array - see the else branch. If the value is non-empty, then there is another nestedif check which checks whether the value is a string and in such case it is converted to array; else it is assumed the value is an array and nothing is done.
In my gulp task, I'd liked to do something like this.
module.paths
is a predefined variable containing all the node_modules search paths to find installed packages. It returns already an array in the current form:This hasn't worked as expected, so I had to convert it to a string instead.
Then I passed that into my sass compile task.
I guess I found the issue here:
gulp-sass/index.js
Lines 122 to 134 in c04bb67
It only checks for strings rather than for a path array. Is it safe to submit a PR for this change, or is there any reason more technical reason behind the check for the string story?
Happy to contribute this small adjustment.
The text was updated successfully, but these errors were encountered: