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

@i2i3i/test-pair-checker

v0.9.2

Published

This checks corresponding test file existance based on those names.

Downloads

4

Readme

Description

This packages aims to list up test target files and those corresponding test files.

You can confirm that which test files are prepared and not.

Usage

  • Install
npm i --save-dev @i2i3i/test-pair-checker

yarn add -D @i2i3i/test-pair-checker

pnpm add -D @i2i3i/test-pair-checker
  • Execution

Prepare a config file test-pair-checker.config.{js,cjs} under your root directory.

// js
const config = {
  // Place all directories where your target files exist.
  targetDirs: [],

  // Set ignore patterns from the above.
  ignorePatterns: [],

  // Place the directory that your test files exist.
  testDir: "",
};

export default config;

// Or cjs
module.exports = {
  targetDirs: [],
  ignorePatterns: [],
  testDir: "",
};
npm pair-check

yarn pair-check

pnpm pair-check

Example

If you have a project like the following, the setting goes like..

.
├── src
│   ├── components
│       ├── custom-button.tsx
│       ├── custom-input.tsx
│   ├── wrapper
│       ├── custom-provider.tsx
│   ├── tests
│       ├── components
│           ├── custom-button.test.tsx
const config = {
  targetDirs: ["src"],
  ignorePatterns: ["**/wrapper/**"],
  testDir: "tests",
};

export default config;

Execution results in the below.

$ npm pair-check

------------------------------------------------------
The number of test target files 2
The number of test files 2
The number of matched test files 1
------------------------------------------------------
You must implement corresponding test files for the following files.
 custom-input.tsx

Contributing

Any PRs are welcome.