I'd really like to get this markdown lib into the nodejs/npm ecosystem, since it's pretty nice and definitely the most full-featured pure-js markdown parser.
TJ has renamed his "markdown" lib to "discount", which makes more sense, since it's really just nodejs bindings to the C discount lib. I'd have used that, but it doesn't compile easily on Solaris, and also doesn't expose as much of the parser goodies.
These two changes make the package easily compatible with express (currently the go-to nodejs web framework). The version is bumped so that it can be clear that it is a break from the 0.1.x "markdown" package, although the exposed nodejs API is backwards compatible with the index.js that I added.
If you would like to move the stuff in the npm overlay in the package.json out to the top-level object, then that would be fine with me, of course, but I didn't want to disturb anything that you might be using it for.
Ash Berlin is now an owner of the "markdown" package name on npm's registry, so you should be able to publish this without any problems.
I'd really like to get this markdown lib into the nodejs/npm ecosystem, since it's pretty nice and definitely the most full-featured pure-js markdown parser.
TJ has renamed his "markdown" lib to "discount", which makes more sense, since it's really just nodejs bindings to the C discount lib. I'd have used that, but it doesn't compile easily on Solaris, and also doesn't expose as much of the parser goodies.
These two changes make the package easily compatible with express (currently the go-to nodejs web framework). The version is bumped so that it can be clear that it is a break from the 0.1.x "markdown" package, although the exposed nodejs API is backwards compatible with the index.js that I added.
If you would like to move the stuff in the npm overlay in the package.json out to the top-level object, then that would be fine with me, of course, but I didn't want to disturb anything that you might be using it for.
Ash Berlin is now an owner of the "markdown" package name on npm's registry, so you should be able to publish this without any problems.