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

esdoc-member-plugin

v1.0.0

Published

An ESDoc plugin that properly reports getter/setter properties as a single member variable

Downloads

45

Readme

ESDoc Member Plugin

Several people had requested that class getters and setters be documented as member properties. I wanted this result as well, and wrote a plugin to achieve it.

ESDoc is a nice framework, but it lacks in the templating area. In order to indicate that a property is readonly or writeonly, it seems that I will have to completely fork the esdoc-publish-html-plugin in order to make this small change to the generated output. This isn't a viable approach since some other author would have to do the same thing to make her change to the published output, thereby ignoring my own.

Because of this, if you want to indicate that your property is readonly or writeonly, you will have to add that fact to your description.

Install

npm install esdoc-member-plugin

Config

{
  "source": "./src",
  "destination": "./doc",
  "plugins": [
    {"name": "esdoc-member-plugin"}
  ]
}

Usage

export default class MyClass {

  /**
   * This is the readable comment
   */
  get prop1() {
  }

  /**
   * This is the writeable comment
   *
   * @param value
   */
  set prop1( value ) {}

  /**
   * This is a read-only member property
   * @type {string}
   */
  get prop2() {}

  /**
   * This is a write-only member property
   */
  set prop3( value ) {}
}

LICENSE

MIT

Author

oravecz