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

eslint-plugin-directory-mirror

v1.0.1

Published

An ESLint rule for mirroring directory structures.

Downloads

14

Readme

eslint-plugin-directory-mirror

NPM Version

An ESLint rule for mirroring directory structures.

Use cases:

  • Ensure that every unit test file has a corresponding source file
  • Ensure that every source file has a corresponding unit test file
  • etc.

Installation

Execute the following command within your project's root directory:

npm i --save-dev eslint-plugin-directory-mirror

ESLint Configuration

Add directory-mirror to the plugins section of your .eslintrc file:

{
  plugins: ["directory-mirror"],
}

Plugin Configuration

There is only one rule within this plugin also named directory-mirror.

This rule has one configuration option which you can use to specify the directories that should be mirrored. Let's use an example to understand the option:

{
  rules: {
    "directory-mirror/directory-mirror": [
      "error",
      {
        "mirrors": [
          { forEach: { dir: "test", ext: ".test.ts", recursive: true }, require: { dir: "src", ext: ".ts" } },
          { forEach: { dir: "src", ext: ".ts", recursive: true }, require: { dir: "test", ext: ".test.ts" } },
        ],
      },
    ],
  },
}

The option has a mirrors array with objects describing the mirrored directories.

Read the object like this: forEach of these files require in the directory dir a file with the extension ext and the same name (without extension and including sub directory).

For the example above this means:

  • For every test file with the extension .test.ts in the test folder there has to be a corresponding source file with the extension .ts in the src folder.
  • And for every source file with the extension .ts in the src folder there has to be a corresponding test file with the extension .test.ts in the test folder.