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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@apib/2postman

v1.2.3

Published

Convert API Blueprints to Postman Collections

Readme

API Blueprint to Postman

Quickstart

  1. Install the package globally

    npm i -g @apib/2postman
  2. Obtain an API blueprint definition file. This is usually created with markdown using API blueprint syntax. You can then feed this blueprint into the following command to have a Postman collection generated from it.

  3. Run the command to generate a Postman collection and environment

    apib2postman <your-blueprint.apib> -o collection.json -e environment.json

Command Line Options

apib2postman <api-blueprint.apib> [options]
  • -o <output>, --output <output>

    Default stdout

    Specify a file for where the collection will be saved.

  • -e <env-output>, --environment <env-output>

    Default API.postman_environment.json

    Specify a file for where the environment template will be saved.

  • -t <test-template>, --testTemplate <test-template>

    Default templates/postman/actions/js-tests.hbs

    Specify a handlebar template to be used for each action's Postman tests. Variables are listed below which can be used within the template.

Postman Test Template

Some JS tests have been created which get templated and attached to every action. The default tests exist at templates/postman/js-tests.hbs

This template is applied to every action and the variables which get passed to this template are as follows:

| Name | Description | Example | | ---- | ----------- | ------- | | pathName | The path of the group collection as a standardized name. | networkDevices_ for /api/networkDevices/:id | | isPageable | Returns true if the response schema has a collection within | true | | sortParams | The accepted sort parameters parsed from the sort query parameter description | [ "name", "category" ] | | request | The same request definition passed to the postman collection template | { } | | response | The same response definition passed to the postman collection template | { } |