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

docincode

v1.1.3

Published

Generate API documentation as JSON from comments in your code.

Downloads

14

Readme

docincode

Generate API documentation as JSON from comments in your code.

Installation

npm install --save docincode

Usage

In your projects javascript files, add comments anywhere and they will be collected and merged by docincode to create an array of versions.

Only comment blocks that start with (docs): {RESOURCE_NAME}@{VERSION} will be included.

If no documentation can be found for a resource in a specific version, it will be taken from the last version that had docs. See the example codebase for a more verbose example.

For example. Given you have the following code somewhere in your src folder:

export default async function presentPerson () {
  return {
    /*
      (docs): presenters.person@v2
      type: View
      inputs:
        fullName: string | required | the first name and last name of the person
    */
    v2: (person) => {
      return {
        fullName: `${person.firstName} ${person.lastName}`
      };
    },

    /*
      (docs): presenters.person@v1
      type: View
      inputs:
        firstName: string | required | the first name of the person
        lastName: number | required | the last name of the person
    */
    v1: (person) => {
      return {
        firstName: person.firstName,
        lastName: person.lastName
      };
    }
  };
}

When you run docincode, like follows:

import docincode from 'docincode';

const versions = await docincode(
  path.resolve(__dirname, './src/**/*.js')
);

Then you will receive the following versions:

versions === [
  {
    "name": "v2",
    "notations": [
      {
        "id": "presenters.person",
        "version": "v2",
        "inputs": {
          "fullName": "string | required | the first name and last name of the person"
        }
      }
    ]
  },
  {
    "name": "v1",
    "notations": [
      {
        "id": "presenters.person",
        "version": "v1",
        "inputs": {
          "firstName": "string | required | the first name of the person",
          "lastName": "number | required | the last name of the person"
        }
      }
    ]
  }
]