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

@designory/build-diff

v0.3.2

Published

A small CLI utility to compare two "build" folders, and copy out the differences between them.

Downloads

17

Readme

Build Diff

npm version

A small CLI utility to compare two "build" folders, and copy out the differences between them.

Requirements

Both of these come standard with macOS and probably most linux/unix flavors.

Install

$ npm install -g @designory/build-diff
# or
$ yarn global add @designory/build-diff

Usage

$ build-diff [options] <old-build-directory> <new-build-directory>

Options

  -q, --quiet          Hides progress as it compares the directories. Defaults to false.
  -j, --json           Outputs results as JSON. Defaults to false.
  -o, --output <name>  Name of the output folder and ZIP file. Defaults to "build_for_upload".

Examples

Standard Example

Given two folders old/ and new/, whose contents are shown below:

old/
├── deleted.txt
├── unchanged.txt
└── updated.txt

new/
├── new.txt
├── sub/
│   └── file.txt
├── unchanged.txt
└── updated.txt

Diffing the two folders yields:

$ build-diff old new
Comparing "old" against "new"...
Diffing directories... Done
Parsing diff results... Done
Copying over changed files... Done
Zipping changed files... Done

The following files were deleted:
  deleted.txt


The following files were changed:
  new.txt
  sub
  updated.txt

All changed files have been copied to build_for_upload, and zipped in build_for_upload.zip

--quiet and --json Flags

When using the --quiet and --json flag, I can pipe the output to jq and view the results as a formatted JSON string.

$ build-diff --quiet --json old new | jq
{
  "filesDeleted": [
    "deleted.txt"
  ],
  "filesChanged": [
    "new.txt",
    "sub",
    "updated.txt"
  ],
  "outputDir": "build_for_upload",
  "outputZip": "build_for_upload.zip"
}

--output Flag

To specificy a different output directory and zip name, simply set the --output argument.

$ build-diff --output=my_folder old new

...

All changed files have been copied to my_folder, and zipped in my_folder.zip

License

MIT