The fix merged in #92 isn't available through npm install sassdown about sassdown HOT 1 CLOSED

For anyone that, like me, isn't yet too familiar with npm, and is getting this issue without knowing how it should be handled properly. I'm leaving here how I sorted it in my end, since this really isn't an issue with sassdown.

If you're using [email protected] and you're getting the error Warning: Path must be a string. and need to include a fixed version of sassdown to sort this out, you can update your package.json to point to this repository, specifically commit 8d9dc78 which includes a fix and be safeguarded regarding future merges or updates to master, although you might still want them anyway.

"devDependencies": {
    "sassdown": "git://github.com/nopr/sassdown.git#8d9dc78"
}

This actually applies to any npm dependency, if you need to apply a fix, just fork the project, apply the fix, push it to your fork, open a pull request and in the meantime point the dependency to your fork repo.

from sassdown.