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

postmoon

v2.1.1

Published

Run your postman tests without postman and without server.

Downloads

3

Readme

Warning: ALFA status, Not stable at all, everything can change.

postmoon

Startup

As glitch project

  1. Go to https://glitch.com/
  2. Click on "New project"
  3. Click on "Clone from git Repo"
  4. Enter https://github.com/hacknlove/postmoon-glitch

As node project

  1. execute:
mkdir postoom-example
cd postmoon-example
npm init -y
npm i @hacknlove/postmoon
  1. Edit your package.json and set
  "scripts": {
    "start": "nodemon -e js,json --exec 'npm run postmoon'",
    "postmoon": "postmoon"
  },
  1. Execute npm start

As bare folder

  1. execute:
mkdir postoom-example
cd postmoon-example
`npx nodemon -e js,json --exec 'npx postmoon'`

tests

Write your tests in files, you can all the postman's API.

If postmoon lacks of some postman's API characteristic you would like to use, please open an issue at issues

You cannot use the filenames global.js, environment.js and requests.js

environment variables

You can set your global and environment variables in the files global.json and environment.json

Each each scenario starts with a fresh and clean copy of the variables.

{
  "variableName": "variableValue",
  "and": "so on"
}

requests

If you want to use pm.sendRequest() you can set request globaly by the file requests.js

var requests = [
  {
    url: /regexp/,
    code: 200
    response: {
      ok: true
    }
  },
  {
    url: /regexp/,
    handler (request) {
      return {
        code: 200
        response: {
          ok: true
        }
      }
    }
  }
]

scenarios

Write the scenarios that are going to be used to each test your tests in a .json file with the same name as the test .js file

{
  "global": {
  },
  "environment": {
  },
  pass: 3,
  fail: 0,
  requests: [

  ],
  "scenarios": {
    "scenarioName": {
      "global": {
      },
      "environment": {
      },
      pass: 3,
      fail: 0,
      requests: [

      ],
      response: {

      }
    }
  }
}