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

routedoc

v0.0.3

Published

a tool for documenting and generating routes.

Downloads

11

Readme

Build Status codecov.io

routedoc — documentation for routes.

routedoc is a tool for documenting and generating urls.

Motivation

Urls are important and having a tool that allows them to be documented in one place helps developers maintain and evolve them as their site/app grows and changes. Many backend frameworks have their own routing built-in, but rarely can you use those routes in other frameworks, other backends, or even on the client-side. The goal of this project is to provide a flexible and human-readable format to document urls that can be used by various clients, backends, and environments.

Installation

To install and use as a module in your nodejs toolchain, run:

npm install routedoc

To install as a command line program, run:

npm install routedoc -g

Example

/**
 * Api endpoint for searching the database
 * @name api-search
 * @param {string} q - text to query for.
 * @returns {SearchResultsJson}
 */
GET /api/:table/search

Running the above through routedoc, like:

routedoc --conf ./routes

-- or --

routedoc < ./routes

will generate the following JSON:

[{
  "method": "GET",
  "name": "api-search",
  "doc": "Api endpoint for searching the database",
  "path": {
    "value": "/api/:table/search"
  },
  "params": {
    "q": {
      "doc": "text to query for.",
      "type": {
        "type": "NameExpression",
        "name": "string"
      }
    },
    "table": {
      "type": {
        "type": "NameExpression",
        "name": "string"
      },
      "doc": null
    }
  },
  "returns": {
    "type": {
      "type": "NameExpression",
      "name": "SearchResultsJson"
    },
    "doc": null
  },
  "tags": {}
}]

From there, it's up to you what you do with the JSON. You can transform it in to something that your framework of choice consumes, generate html docs, automatically create HTTP acceptance tests, or use one of the libraries below.

See more examples here.

Libraries

TODO

  • [ ] Support multiple route files
  • [ ] Api for generating urls from a route (e.g., routedoc.toUrl('api-search', { q: 'routedoc'}) => '/search?q=routedoc')
    • Note this will probably exist in it's own repo.
  • [ ] ...?

License

MIT