Sassdown should be decoupled from Grunt about sassdown HOT 7 OPEN

Hi,

I've read a couple of issue about this topic. I'm moving some of my project from grunt to gulp and, since i'm using sassdown and find it very usefull, I'd like to know if I can help in any way.

I'm pretty experienced in JS/Grunt and a bit in node. Never did a gulp-capable module though...

Bye!

from sassdown.

Hi I've managed to remove grunt deps.

The codebase is still a bit raw, but tests output is the same as the grunt version:

https://github.com/fevrcoding/node-sassdown

from sassdown.

Sorry for the multiple posts.

Here is the wrapped grunt plugin:

https://github.com/fevrcoding/grunt-sassdown

from sassdown.

Hi, @dwightjack - thanks for your contribution on this. Have you looked at the 1.0.0 branch? I've done quite a bit of this already. https://github.com/nopr/sassdown/tree/feature/1.0.0

from sassdown.

Ops, sorry

didn't had any feedback on this issue so i thought to contribute.

I'll take a look to 1.0.0 and contribute on that :)

from sassdown.

👍 This would be a useful feature. I'll use grunt.loadNpmTasks in the meantime 💅

from sassdown.

Hi I took a look at the codebase.
I'm not sure using the context of module.exports as instance configuration options is a good idea. It's an edge case, I think, but if someone wants to use the library twice he will end up sharing all the settings.

I think a better solution would be to use a constructor.

from sassdown.