New version to be released on NPM?

[mb185390]

I notice that the README mentions the --template <filename or path> option but this isn't available in the most recent version from NPM (0.0.13).

I could really use this option and wondered if there is any intention to update NPM with the latest version?

[cwjohan]

The intention is there. I'm not set up very well to do it right now, but I'll look into it.

…

On Mon, Nov 20, 2017 at 6:57 AM, iexp-935 ***@***.***> wrote: I notice that the README mentions the --template <filename or path> option but this isn't available in the most recent version from NPM (0.0.13). I could really use this option and wondered if there is any intention to update NPM with the latest version? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#25>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AH5q3NQvqMwFpIUXSbZQOKAXcU-euaoqks5s4ZNGgaJpZM4QkYnC> .

[mb185390]

Thanks :)

[SylvainFourny]

I will also be glad if a new version is officially released. Can we do something to help you ?

[cwjohan]

Anybody want to take over this project? I no longer have a suitable development environment.

…

Sent from my iPhone

On Jan 10, 2018, at 7:26 AM, SylvainFourny ***@***.***> wrote: I will also be glad if a new version is officially released. Can we do something to help you ? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[SylvainFourny]

I'm not used to do this but I can try.

• Make a release on github and npm
• Indicate in the readme that the project is not anymore maintained and that users can use alternative (like marked)

What do you think ?

[cwjohan]

Sylvain, you could fork this project and do a release on Github and on NPM (*https://www.npmjs.com/package/markdown-to-html <https://www.npmjs.com/package/markdown-to-html>)*. There already are 27 forks of this project, but I don't see any of them on NPM -- at least none are obvious to me. My own NPM package is still there, but you could create one with a similar name, such as markown-to-html2, or whatever. You probably should take this on only if you are willing to spend some time (maybe two to four hours per month) to keep the dependencies up to date (perhaps the most difficult task), keep the code compatible with the latest node.js, and to deal with the occasional request for new features or bug fixes. This also means, of course, maintaining an up to date development environment. What do you think? Cheers, Craig Johannsen

…

On Fri, Jan 12, 2018 at 2:47 AM, SylvainFourny ***@***.***> wrote: I'm not used to do this but I can try. - Make a release on github and npm - Indicate in the readme that the project is not anymore maintained and that users can use alternative (like marked) What do you think ? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AH5q3Kg5X0tCeRLlcT5WOiCvif5AOpT-ks5tJzhGgaJpZM4QkYnC> .

[yaboililc11]

No luck?