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

@rolyrosales23/colrun

v1.1.2

Published

Run postman collection cli (based on newman)

Downloads

2

Readme

Overview

Collection runner CLI for postman (based on newman). Run postman collections with optionals environment and iteration data.

Install

npm install -g @rolyrosales23/colrun

Usage

The first step is to define the global configuration

colrun init configfile.json

Configuration file must have this shape

{
  "apiKey": "postman-api-key",
  "environments": {
    "dev": "b431787c-484f-428f-b764-6f33d1289d00",
    "pre": "4950bc82-929d-43bb-a43b-f010e0dfea4b"
  },
  "defaultEnvironment": "dev"
  "collections": {
    "mycol": {
      "collectionId": "5e8de6f6-0595-4458-a954-11356491594e",
      "folder": "folder_name",
    },
    "othercol": {
      "collectionId": "32a139dd-7e4b-49b6-9737-7fa4f611d5ee",
    }
  },
  "defaultCollection": "othercol"
}

There is a config subcommand to adjust any detail in global configuration

colrun config --help

Multiple collections and environments could be defined. At least one collection must be configured.

Optional "folder" property is use to run only one folder inside the given collection (leave empty to run the entire collection).

To log all responses to an output directory use -d or --detailed flag.

colrun -e pre --detailed

If a collection or environment is not supplied with commandline arguments then the ones defined at defaultCollection or defaultEnvironment properties are going to be used.

Examples

# Run default collection with default environment using datafile.json as iteration data
colrun datafile.json

# Run default collection with dev environment using datafile.json as iteration data
colrun datafile.json -e dev

# Run mycol collection with default environment without iteration data
colrun -c mycol

# Run using defaults
colrun -r