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

five-bells-integration-test-loader

v1.5.3

Published

Intelligent dependency loader for integration tests

Downloads

4,670

Readme

five-bells-integration-test-loader

Purpose

The Five Bells integration tests will test a module against the latest versions of each other module. If it is testing the branch of a module, it will prefer branches of the same name for other modules.

However, the version of the integration tests themselves are hard-coded in each module's package.json file.

That means that when a new component requires a change to the integration tests, the integration test version must be bumped in every single component. It also means that we often need to "[skip tests]" when making changes to the tests themselves.

This module fixes this problem by applying the same rules we apply to the modules under test to the integration tests themselves. In other words, it will automatically test using the latest master of the integration tests or using a branch of the same name.

Usage

Adding tests to a module

If a module should be tested as part of the integration tests, it needs to depend on this loader:

npm install --save-dev five-bells-integration-test-loader

And it needs to specify which integration test module to use in its package.json:

{
  "name": "foo",
  "version": "1.0.0",
  "config": {
    "integration-test-loader": {
      "module": "five-bells-integration-test",
      "repo": "interledgerjs/five-bells-integration-test"
    }
  }
}