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 🙏

© 2026 – Pkg Stats / Ryan Hefner

infiniswiss-integration-tests-runner

v0.0.3

Published

Integration tests runner

Readme

###Integrations tests

#####Description

Integration tests for checklist tool based on postman collections

#####Install and run then project

  1. Install npm install
  2. Run in development npm run start

####Project structure

integration-tests-runner
│   README.md
│
└───testing-data // postmant collection and environments which are listed in `integration-tests-config.json`
└───integration-tests-config.json // config file for test runner
└───tests-definitions // all possible collections for testing
    │   checklist-integration-tests.postman_collection.json
  1. Publish package npm publish

####Usage

  1. This package is needs to be installed as a dependency in your project and then you can use postman to create a test collection and export it as well as the environement variables for it.
  2. Then you need to write your config as json file similar to integration-tests-config.jso
{
    "reporters": "cli",
    "environments": {
        "production": "...path to postman environment variables exported for production",
        "testing": "...path to postman environment variables exported for testing"
        ... as many environments as you have,
    },
    "postmanCollections": [
        "...path to exported collection from postman you can run as many collections as you want  they will run on the specified environment variables listed in the command line"
    ]
}
  1. Run the tests "node ./node_modules/integration-tests-runner/lib/main.js -config="./integration-tests-config.json" --environment="testing"

####Important before adding/updating tests Don't define authorization on folder and use inherit from parent cause it generates bugs. Define authorization on each endpoint as NTLM and manually set the user and password