npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

doctomd

v1.2.1

Published

Javadoc to Markdown Converter

Readme

Javadoc to Markdown Converter

Converts JavaDoc to Markdown. Based on delight-im/Javadoc-to-Markdown

  • Can convert a complete project
  • support for frontmatter / standalone files
  • Customize each Markdown File with Pre- and Post-Markdown Files (will be added in front or after content)
  • Modules (can be added on GitHub)

⚠️ will delete the specified output directory before generating!

Installation

npm i -g doctomd

Usage

doctomd \
--input {input directory} \
--output {output directory} \
[--front {frontmatter directory}] \
[--pre {pre directory}] \
[--post {post directory}] \
[--module code] \
[--module hyphen] \
[--module link]

| flag | description | required | | -------- | --------------------------------------------------------------------------------------- | -------- | | input | directory with input Java files | ✅ | | output | directory for output Markdown files | ✅ | | front | directory with files for frontmatter. Can / Should also be used for standalone files | ❌ | | pre | content of files in this directory is put after the heading and before the doc content. | ❌ | | post | content of files in this directory is put after the doc content | ❌ | | module | currently available modules: code, hypen, link | ❌ |

For the files in the frontmatter / pre / post directories to matched with the input Java files, the directory structure and file names should be exactly the same (excluding the file extension)


Contributing:

Feel free to post issues and develop this further.

Testing your changes

  • test directory should look like this:
    test
    ├─front
    │ └─...
    ├─input
    │ └─...
    ├─output
    │ └─...
    ├─post
    │ └─...
    └─pre
      └─...
  • npm run test
    (node .\\bin\\doctomd --input test/input --output test/output --front test/front --pre test/pre --post test/post --module code --module hyphen --module link)