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

clone-check

v1.1.1

Published

A utility to check whether a directory is an exact clone of another directory.

Downloads

2

Readme

clone-check

A utility to check whether a directory is an exact clone of another directory. This might be useful, if you have some source code in your repository, that is created by a template. For example, if you have a create-react-app template, and an instance of that template in the same repo. This is helpful for testing purposes, because you don't need to re-create a new app from the template every time you want to test something. The problem in this case is that you have to make sure to keep the test app and the template in sync. In this scenario the clone-check utility will come in handy: It will check whether your test app and template are the same, by running just a single script command.

Install

yarn add --dev clone-check

Usage

Add a script to your package.json to run the clone check:

  "scripts": {
    "test": "...",
    "build": "...",
    "template:check": "clone-check -m \"The template is not up-to-date!\" src template tmp test"
  },

Command line interface

Usage: clone-check [options] <sourceDir> <cloneDir> [ignorePatterns...]

Arguments:
  sourceDir                The source directory
  cloneDir                 The clone directory to check
  ignorePatterns           Files and directories to ignore when checking the clone (glob syntax)

Options:
  --verbose                Increase the console output
  -m, --message <message>  An optional error message to show when the clone does not match the source
  -h, --help               display help for command

Examples

Basic usage:

clone-check src clone

Use custom error message:

clone-check -m "The clone directory does not have the same contents as the src directory!" src clone

Relative source and clone directories:

clone-check . ../other

Absolute source and clone directories:

clone-check C:/git/my-app/src C:/git/my-app/clone

Ignore node_modules directory (in all subdirectories):

clone-check src clone **/node_modules/**

Ignore test directory (only in root):

clone-check src clone test/**

Ignore config.js file (only in root):

clone-check src clone config.js

Ignore test files (in all subdirectories):

clone-check src clone **/*.test.js

Multiple ignore patterns:

clone-check src clone **/*.test.js **/*rc.js config.js **/node_modules/**