After a (far too long!) period of neglect, this addresses all outstanding issues and significantly changes the approach to the Markdown parser. I also dropped node 0.x support in https://github.com/SparkartGroupInc/gulp-markdown-to-json/commit/b91df033936bbacd72f6982a30e919ba4c9c0b40 but published a 0.4.0 release preceding this for anyone who wants more current dependencies without dealing with the other breaking changes here.
Since writing this originally I used markdown-it on a couple projects and really loved the pluggable approach to features. Remark is an interesting effort that's doing something similar. Point is: there continues to be a lot going on (as with everything JS) and I don't want to impose my preferences. This plugin has much more to offer than being a wrapper, so I'm focusing on that.
More details in the newly added changelog RELEASES.md
todo
[x] YAML exceptions still break the stream, is Promise.all to blame?
After a (far too long!) period of neglect, this addresses all outstanding issues and significantly changes the approach to the Markdown parser. I also dropped node 0.x support in https://github.com/SparkartGroupInc/gulp-markdown-to-json/commit/b91df033936bbacd72f6982a30e919ba4c9c0b40 but published a 0.4.0 release preceding this for anyone who wants more current dependencies without dealing with the other breaking changes here.
Since writing this originally I used markdown-it on a couple projects and really loved the pluggable approach to features. Remark is an interesting effort that's doing something similar. Point is: there continues to be a lot going on (as with everything JS) and I don't want to impose my preferences. This plugin has much more to offer than being a wrapper, so I'm focusing on that.
More details in the newly added changelog
RELEASES.mdtodo
Promise.allto blame?