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

rapidocgen

v1.2.1

Published

Restful API documenation generator

Downloads

27

Readme

RAPIDocGen v1.2.1

Simple script to transform postman test collections v2.1 to a swagger file

Installation

Using npm

$ npm install -g rapidocgen
Usage
 $ rapidocgen <filepath> [<outputPath>]
 $ rdg <filepath> [<outputPath>]

Known Issues

  • Only application/json & text/plain is parsable
  • --help command is not implemented
  • Collection structure must follow Collection -> folders -> saved requests

Guidelines

To parse a variable path use postman's as the following example

Postman variable path example

Edit the collection to add the matching variables with their value so you can test your requests

Postman variable path example 2

Request responses will use postman's to build example responses' If no responses are available default will be 200: 'ok'

Imgur

Changelog

v1.2.1

  • Fixed issue with requests without body that caused script to abort (sorry for the inconvenience)
  • Added feedback when the command terminates successfully

v1.2.0

  • RAPIDocGen abbreviation command added, rdg now available
  • Script will now parse urlencoded body
  • Fixed an issue where $ref paths would have spaces in between, causing yml errors
  • Nested objects wont destroy response objects now (Will keep an eye on this one)
  • IMPORTANT: Currently the script is unable to parse multiple same response code, if there are any, response objects will be created and only the last will be shown automatically

v1.1.2

  • Fixed an issue where path variables wouldn't be parsed correctly into path parameters
  • Script won't crash now if there is a request outside a folder, it won't parse it yet
  • Modulirized code

v1.0.5

  • Output path issue fixed, user can now specify path & file name, Default is set to 'RAPI_Docs.yml'
  • Updated docs with variable params example & default response

v1.0.0

RAPIDocGen v1.0.0