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

moose_like_swagger

v0.0.2

Published

Downloads

7

Readme

moose (like_swagger)

Moose is a command-line tool that looks for YAML-formatted Swagger resource declarations, stitches them together, and outputs json resource files.

The moose himself

Example:

Let's say you have the following Javascript code in views.js.

/*
$$$
---
swaggerMeta:
  name: user.json
  description: Operations for users
resourcePath: /user
basePath: url
swaggerVersion: 1.1-SHAPSHOT.121026
apiVersion: 0.1
apis:
$$$
*/
// USER resource
/*
  $$$
  - # begin API endppoint
    path: /user
    description: Create a user
    operations:
      - # create a user (createUser)
        parameters:
        -
          description:        Create instance of User
          dataType:           user
          required:           true
          valueTypeInternal:  models.user.User
          allowMultiple:      false
          paramType:          body
        httpMethod:           POST
        responseTypeInternal: models.user.User
        nickname:             createUser
        responseClass:        user
  $$$
  ## createUser ##
  API endpoint for creating a new user.
  Accepts express **req**uest and **res**ponse objects.
*/
exports.createUser = function (req, res) {
    users.create(req.body, respond(res))
}

/*
$$$
---
swaggerMeta:
  name: resources.json
  description: API resource definition
basePath: url
swaggerVersion: 1.1-SHAPSHOT.121026
apiVersion: 0.1
apis:

$$$
*/

Calling moose -o spec views.js will

First. extract the YAML data between the '$$$' delimiters. Creating a YAML multi-doc that looks like so:

    ---
    swaggerMeta:
      name: user.json
      description: Operations for users
    resourcePath: /user
    basePath: url
    swaggerVersion: 1.1-SHAPSHOT.121026
    apiVersion: 0.1
    apis:
      - # begin API endppoint
        path: /user
        description: Create a user
        operations:
          - # create a user (createUser)
            parameters:
            -
              description:        Create instance of User
              dataType:           user
              required:           true
              valueTypeInternal:  models.user.User
              allowMultiple:      false
              paramType:          body
            httpMethod:           POST
            responseTypeInternal: models.user.User
            nickname:             createUser
            responseClass:        user
    ---
    swaggerMeta:
      name: resources.json
      description: API resource definition
    basePath: url
    swaggerVersion: 1.1-SHAPSHOT.121026
    apiVersion: 0.1
    apis:

Second. Convert the YAML into two separate JSON documents in the spec folder

// resources.json
{
  "basePath": "url",
  "swaggerVersion": "1.1-SHAPSHOT.121026",
  "apiVersion": 0.1,
  "apis": [
    {
      "path": "/user.{format}",
      "description": "Operations for users"
    }
  ]
}

// user.json
{
  "resourcePath": "/user",
  "basePath": "url",
  "swaggerVersion": "1.1-SHAPSHOT.121026",
  "apiVersion": 0.1,
  "apis": [
    {
      "path": "/user",
      "description": "Create user",
      "operations": [
        {
          "parameters": [
            {
              "description": "Create instance of User",
              "dataType": "user",
              "required": true,
              "valueTypeInternal": "models.user.User",
              "allowMultiple": false,
              "paramType": "body"
            }
          ],
          "httpMethod": "POST",
          "responseTypeInternal": "models.user.User",
          "nickname": "createUser",
          "responseClass": "user"
        }
      ]
    }
  ]
}