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

jsusedocs-core

v1.1.0

Published

A libary for interacting with jsdocs

Downloads

7

Readme

JsUseDocs - core

A tool/library to parse and alter jsdocs in files with the intent on supporting JsDoc and JsDoc style comments on code. This is to feed a later project to develop a interactive GUI for jsdocs however can act as a stand alone, this however is a way to guarantee regular feature releases and updates

The idea is not just to make it easier to work with jsdocs but also to be able to make it easily expandable to support plugins and custom tags, for example to add react or electron specific comments. Adherence to jsdoc standards is not strictly promised.

Goals

  • To allow for tooling to integrate with jsdoc comments
  • To provide a flexible system to support multiple frameworks and js structures
  • To promote the use of clear understandable code

Is this a replacement for jsdoc?

No it can be used alongside standard jsdoc and has minimal feature overlap. This allows for interacting with jsdoc in js files programmatically as and when needed and not a way to compile it to a template

Common use cases

  • Adding to tests to check they are Doc'd correctly
  • Creating tools to automatically document a codebase
  • creating interactive tools to explore a codebase

What are you defining a doc as?

So in an aim to support all things we are in danger of just returning just a whole document. our rules are to be(loosely) :

  • all docs start with /*_ and end in _/
  • the line below the doc is the thing being documented (function, variable etc)
  • All parameters/tags are formatted between @tagname {variableA} variable description and @tagname description

These are preliminary rules for development please feel free to suggest more. I haven't really checked them against jsdoc either so I am certain to find edge cases but as time goes on it is hoped we can refine these rules to remain flexible but prevent the library returning junk.