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

@borgar/jsdoc-tsmd

v0.2.2

Published

A (limited) JSDoc template that prints Markdown and TypeScript declaration files

Downloads

14

Readme

jsdoc-tsmd

A JSDoc template for small projects that can emit Markdown docs or TypeScript types.

Not really recommended for use as it only implements the few parts of JSDoc that the author has use for. Likely the project will die as TS tooling gets better over time.

Setting up

Set this up like any other JSDoc template. Start by installing the package:

npm i -D @borgar/jsdoc-tsmd

Then add a config file, which it might look something like this:

{
  "source": {
    "includePattern": ".+\\.js(doc|x)?$",
    "excludePattern": "((^|\\/|\\\\)_|spec\\.js$)"
  },
  "opts": {
    "template": "node_modules/@borgar/jsdoc-tsmd",
    "destination": "console",
  }
}

Running jsdoc -c myconfig.json src should then emit some Markdown docs (given that the sources have valid jsdoc comments in them). See the options below for how do produce TypeScript type declarations.

Options:

Generally, refer to JSDoc's documentation on how to configure it but these options have special meaning here:

  • destination - Where to save the emitted text, using "console" will log the output to the console.
  • output - Set this to "typescript" to emit TypeScript type declarations rather than Markdown docs.
  • validate - When producing type declarations, the output will be run through TypeScript to validate it, if you like living on the edge, you can set this to false to skip this step.

License

MIT