How to handle a sass module import within a sass module import?

[ritchieking]

I recently published a bunch of reusable styles as a sass module on npm (and i have a project generator which creates a bunch of template files and imports that sass module using gulp-sass and sass-module-importer).

The thing is, that sass module is currently set up to depend on another sass module (breakpoint-sass). If I run my project generator, and npm install using npm >= 3.0.0 everything is groovy, since all the dependencies are installed at the the top level. But if I use an older version of npm, then breakpoint-sass ends up tucked away inside the folder where my custom sass module lives, and sass-module-importer can't find it.

The temporary fix I've done for now is just to add breakpoint-sass as a dependency within my project generator (that adds it to the top level dependencies, regardless of npm version). But I'm wondering if there's a real way to allow sass modules to depend on other sass modules...

(Hope that makes sense)

[CameronCarranza]

It sounds somewhat like we may be having the same issue, I just commented in #3 about it.

breakpoint-sass may already be used by something else, what happens if you name it to say, _4192016-breakpoint-sass.scss or something similar, and then try to import it? I'm noticing this extension is ignoring all but the first of a similar name as far as compiling goes on my end.