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 🙏

© 2024 – Pkg Stats / Ryan Hefner

typedoc-plugin-missing-check

v0.4.0

Published

TypeDoc plugin to check for missing or empty documentation.

Downloads

1

Readme

🤷‍♀️ Typedoc Plugin: Missing Check 🤷‍♂️

CI

TypeDoc Plugin to check if typescript documentation is empty or missing.

A plugin for TypeDoc that check TypeScript API documentation actually exists and throws errors when it is accidentally forgotten.

Installation

npm install --save-dev typedoc typedoc-plugin-missing-check

Usage

Usage is the same as documented at TypeDoc.

typedoc src/
# Check only public or higher (default).
typedoc --missing-check-level public src/

# Check only protected and public.
typedoc --missing-check-level protected src/

# Check all.
typedoc --missing-check-level private src/

# Disable missingness checks.
typedoc --missing-check-disabled src/

# Enable more verbose error messages.
typedoc --missing-check-verbose src/

These options can also be configured in your typedoc.json or tsconfig.json like so:

typedoc.json

{
    "missing-check-disabled": false,
    "missing-check-verbose": false,
    "missing-check-level": "public"
}

tsconfig.json

{
    "compilerOptions": {
        ...
    },
    "typedocOptions": {
        "missing-check-disabled": false,
        "missing-check-verbose": false,
        "missing-check-level": "public"
    }    
}

Development

Get setup

git clone https://github.com/neozenith/typedoc-plugin-missing-check
cd typedoc-plugin-missing-check
npm ci

Run a self check since there are no tests just yet.

npm run build
npx typedoc --plugin . src/

Contributing

Report issues on Github, or more appreciated would be opening a pull request and we can collaborate on getting the needed change over the line.

Since you will need to create a fork to open up a new PR, you can also then immediately use your updated version with:

npm install --save-dev https://github.com/{USER}/typedoc-plugin-missing-check/tarball/{BRANCH}

See this Stackoverflow article "How to install an npm package from github directly?" for more details.

Then revert back to using this version once your PR is accepted and published:

npm install --save-dev typedoc-plugin-missing-check

TODO

Next

  • Create jest test suite
  • Handle missing class constructor docs
  • Handle missing method docs

Later

  • Automate process publishing of docs and to npm process after successful CI and merge to main.
  • Automate Github Release page.