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

postgen

v5.0.4

Published

A simple node script to convert postman collections to clean REST client libs for node.

Downloads

2,322

Readme

Postgen

A simple node script to convert postman collections to clean REST client libs for node.

Install

npm install -g postgen

How to use

  • Export your collection from postman as a v2.1 collection.
  • cd into your projects root folder that you want to use the client with.
  • Install fasquest as it is the only dependency of the generated client.
npm install --save fasquest
  • Run postgen for node SDK generation
postgen /path/to/postman/collection.js > YourApi.js
  • Run postgen for web SDK generation
postgen /path/to/postman/collection.js web > YourApi.js
  • View the examples on how to use your newly generated lib.

Examples

Wasps with Bazookas Service

A postman collection of the service:

Generated a class structure:

WaspsWithBazookas
    |
    |___Hive
    |___Wasps
    |___Wasp

Example use of the generation.


const WaspsWithBazookas = require('./WaspsWithBazookasAPI.js')(
  'https://127.0.0.1:4269' // the url to service with no trailing /
);

// Start loadtest for 1second
WWB.Hive.HivePoke({
  "t": "10",
  "c": "50",
  "d": "1",
  "target": "http://127.0.0.1:4269/hive/status"
}).then(response=>{
  console.log(response)
})

// Wait 2 seconds and show the report
setTimeout(async ()=>{
  console.log((await WWB.Hive.HiveStatusReport()))
},2000)

Samples

See the samples folder for the collection used and the generated API from that collection.

Travelling Service

A postman collection of the service:

Generated a class structure:

Travelling
    |
    |___Auth
    |___Groups
    |___User
         |____Current

Example use of the generation.


const Travelling = require('./TravellingAPI.js')(
  'https://127.0.0.1:6969' // the url to service with no trailing /
);

Travelling.Auth.login({
  "username":"test",
  "password":"password1234"
}).then(response=>{
  console.log(response)
})

Samples

See the samples folder for the collection used and the generated API from that collection.

Further Development

The code to do the generation is just some hacky code busted out in a hour. I would love help cleaning it up and making it more feature rich.