Windows. Ugh...

[jonscottclark]

For some reason when using Windows this doesn't work. Used with gulp-sass, and it just hangs on the task. Confirmed that using the importer option by itself, just returning the filename, works fine. Versions of node-sass, libsass, npm, and node were all up-to-date, and node-sass was built with node-gyp correctly.

I looked through the source to see if anything jumped out but I have no ideas currently. I know this is a terrible issue report in terms of information provided but maybe others have had the same problem, or maybe @lennym would be able to figure out if there's some obscure bug within a dependency?

The issue is with a coworker's machine so I can try and get them to provide any more info, or even modify some of the source code itself to try and narrow down the issue. I can try to replicate this on a VM also.

[lennym]

Thanks for raising an issue @jonscottclark - sadly I don't have access to a Windows instance to debug/test this, so I'll leave it open for now in the hope that someone can contribute.

[lennym]

Something that might help shed some light on this though would be a minimal scss file that can reproduce. I'd be keen to know if the same thing can compile if running npm-sass directly rather than through gulp as well.

[GeorgeTaveras1231]

Something I've noticed which may be a cause for this is the use of '/' instead of path.sep when dealing with path logic. I'm currently working on a refactor that fixes some of these but not all. These changes will be added to #12.