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

pits

v1.0.7

Published

Postman integration test utils.

Downloads

25

Readme

pit

A postman integration test utils.
Taking advantage of postman's pre-request script and test-script.
This utils help describe and test your collection with simple syntax.

Caution

Since postman doesn't have clear "scopes" like javascript variables, instead have their own pm.variables.
In order to make scripts work, there will be a few eval() functions in lib/t.js, feel free and inspect the code.
It's only eval() what you code, so please make sure you don't add any danger or malicious script into describe, test or before code blocks.

Install

npm i pits

Project structure (more on example)

src
  |__GitHubApi
  |     |__GetUserSuite.js
  |     |__OtherSuite.js
  |__googleSuite.js
  |__spotifySuite.js
  |
  |__.pit_collection.js
  |__package.json

Suite declaration

.pit_collection.js

const path = require("path");

module.exports = {
  name: "Example Fun Postman",
  suites: {
    includes: ["Suite.js"], // patterns for `suite` file, could be anything.
    dirs: [path.join(__dirname)] // paths where `suite` file should be placed.
  }
};

Define your simple script like example/googleSuite.js

const { describe, before, test } = require("pits");

module.exports = describe("Let's check google", () => {
  before("200", () => {
    console.log("This will be called before sending request");
    console.log("{{request_url}} is hard_code, will be more dynamic later");
    pm.variables.set("request_url", "https://google.com");
  });

  test("200", "Test 200 description", () => {
    pm.response.to.have.status(200);
  });

  before("404", () => {
    console.log("This should call when init");
    pm.variables.set("request_url", "https://google.com/404");
  });

  test("404", "Test 404", () => {
    pm.response.to.have.status(404);
  });
});

Run

node -e 'require("pits").extract()'

This extract() function will use the config from .pit_collection.js file to generate .postman_collection.json into current folder.

If you have newman installed:

newman run test.postman_collection.json

Flow diagram

diagram

TODO

  • Adding variables file.
  • Improve pit_collection.json.