You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After running a npm install -D sassdown, the node_modules/sassdown/tasks/libs/sassdown.js doesn't have fix #92 applied, causing the task to fail.
I'm not familiar with npm publish, but I believe it just never got published?
I managed to have it working by just using npm install -D nopr/sassdown but would definitely welcome a better solution.
The text was updated successfully, but these errors were encountered:
vitorleite
changed the title
The fix merged in #92 isn't available through npm install
The fix merged in #92 isn't available through npm install sassdown
Aug 2, 2017
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 sassdown@0.2.7 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.
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.
After running a
npm install -D sassdown
, thenode_modules/sassdown/tasks/libs/sassdown.js
doesn't have fix #92 applied, causing the task to fail.I'm not familiar with npm publish, but I believe it just never got published?
I managed to have it working by just using
npm install -D nopr/sassdown
but would definitely welcome a better solution.The text was updated successfully, but these errors were encountered: