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 🙏

© 2026 – Pkg Stats / Ryan Hefner

easy-replace-in-files

v2.0.0

Published

CLI to find and replace in files via a JSON config. Supports globs, regex, and placeholders (e.g. $$package__version$$, $$ENV_VAR$$). Great for version bumps and build-time replacements.

Readme

easy-replace-in-files

Find and replace in files via a config file. Supports globs, regex, and placeholders ($$ENV_VAR$$, $$package__version$$).

Requires Node 20+.

Install

npm install --save-dev easy-replace-in-files

Usage

Add easy-replace-in-files.json (or the shorter easy-replace.json) in your project root. If both exist, easy-replace-in-files.json is used. Each rule has files, from, and to; type defaults to "string". Rule shape: files (string or array of strings), from (string or array), to (string or array), type ("string" or "regex").

Basic example

{
  "easyReplaceInFiles": [
    {
      "files": "readme.txt",
      "from": "Stable tag:\\s?(.+)",
      "type": "regex",
      "to": "Stable tag: $$npm_package_version$$"
    }
  ]
}

Run via script (e.g. in package.json: "version": "easy-replace-in-files"):

npm run version

Advanced example

Regex, multiple files/globs, multiple from/to, and placeholders ($$ENV_VAR$$, $$package__version$$):

{
  "easyReplaceInFiles": [
    {
      "files": "readme.txt",
      "from": "Stable tag:\\s?(.+)",
      "type": "regex",
      "to": "Stable tag: $$package__version$$"
    },
    {
      "files": ["src/index.js", "src/utils.js"],
      "from": "OLD_STRING",
      "to": "NEW_STRING"
    },
    {
      "files": "dist/**/*.js",
      "from": ["__BUILD_DATE__", "__BUILD_ENV__"],
      "to": ["$$BUILD_DATE$$", "$$NODE_ENV$$"]
    }
  ]
}

Options

| Option | Description | |--------|-------------| | --dry-run | Show which files would be changed without writing. Use with --verbose to list each file per rule. | | --verbose | Log each rule and succeeded/skipped/failed counts. | | --config <path> | Use a custom config file (default: easy-replace-in-files.json or easy-replace.json in the current directory, first found). Requires a path (e.g. --config my.json); exits with error if missing. | | --help | Show usage and options. | | --version | Show version and exit. |

License

MIT