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

@medable/mdctl-docs

v1.0.73

Published

Medable Developer Client Tools :: Documentation

Downloads

292

Readme

mdctl-docs

Medable documentation tool.

env

Navigate to directory containing an exported environment

export ENV_EXPORT_HOME=/path/to/env/export
cd ${ENV_EXPORT_HOME}

Generate documentation

mdctl docs --module env

By default, documentation is generated in ${ENV_EXPORT_HOME}/docs.

Script Headers

To capture additional information such as version, authors, and summary, please include a JSdoc styled comment to the top of the script file. JSdoc description and examples are rendered using markdown formatting.

/**
 * @file
 * @summary Account creator
 * @version 1.0.0
 *
 * @author Medable Developer
 *
 * @description
 * ```javascript
 * const { email, password, name } = require('request').body;
 *
 * return require('accounts').register({ email, password, name }, {
 *    skipVerification: true,
 *    skipActivation: true,
 *    skipNotification: true,
 *    requireMobile: false
 * });
 * ```
 *
 * @example
 * ```javascript
 * mdctl api POST userCreator --env=dev.example
 * ```
 * @copyright
 *
 * (c)2016-2020 Medable, Inc.  All Rights Reserved.
 * Unauthorized use, modification, or reproduction is prohibited.
 * This is a component of Axon, Medable's SmartStudy(TM) system.
 */

Routes

To capture route parameters (path, body, query, header, and response) please include a JSdoc styled comment describing the route. Routes can be defined within the header of a route script file, or above their coresponding decorator within a library script file.

Route Script

/**
 * @file
 * @summary route script example
 * @version 1.0.0
 *
 * @author Medable Developer
 *
 * @route-param-path {string} id - Resource ID
 * @route-param-body {Object} data - Resource data
 * @route-param-body {string} data.name
 * @route-param-query {string} token - Access token
 * @route-param-header {string} Authorization
 * @route-param-response {Object} resource - Resource
 * @route-param-response {string} resource.id
 * @route-param-response {string} resource.name
 */

Decorator: @route

/**
 * @route c_340_ping - post
 * @param-route-path {string} id - Resource ID
 * @param-route-body {Object} data - Resource data
 * @param-route-body {string} data.name
 * @param-route-query {string} token - Access token
 * @param-route-header {string} Authorization
 * @param-route-response {Object} resource - Resource
 * @param-route-response {string} resource.id
 * @param-route-response {string} resource.name
 */
@route({
  weight: 1,
  method: 'POST',
  name: 'c_340_post',
  path: 'c_340_ping',
  acl: 'role.administrator'
})
post({ req, res, body, next, runtime }) {

    return body('myData')

}

TODO

  • Upgrade to node v12.X (currently v8.16.2)
  • Additional tests for runtime resources
  • Sync with master branch