Sassdown should be decoupled from Grunt

[winstromming]

Problem:

• Sassdown uses grunt methods such as grunt.file.read, grunt.verbose.write, etc. This added dependency makes writing a caller-agnostic module more difficult.

Objective:

• Replace any required methods with other, dedicated third-party modules or core methods if possible. (eg. node-glob, fs-extra, etc.)

[dwightjack]

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!

[dwightjack]

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

[dwightjack]

Sorry for the multiple posts.

Here is the wrapped grunt plugin:

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

[winstromming]

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

[dwightjack]

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 :)

[Trolleymusic]

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

[dwightjack]

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.