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 🙏

© 2025 – Pkg Stats / Ryan Hefner

replace-in-files-cli

v4.0.0

Published

Replace matching strings and regexes in files

Readme

replace-in-files-cli

Replace matching strings and regexes in files

Install

npm install --global replace-in-files-cli

Usage

$ replace-in-files --help

  Usage
    $ replace-in-files <files…>

  Options
    --regex           Regex pattern to find  (Can be set multiple times)
    --string          String to find  (Can be set multiple times)
    --replacement     Replacement string  (Required)
    --ignore-case     Search case-insensitively
    --no-glob         Disable globbing
    --dry-run         Show what would be replaced without making changes

  Examples
    $ replace-in-files --string='horse' --regex='unicorn|rainbow' --replacement='🦄' foo.md
    $ replace-in-files --regex='v\d+\.\d+\.\d+' --replacement=v$npm_package_version foo.css
    $ replace-in-files --string='blob' --replacement='blog' 'some/**/[gb]lob/*' '!some/glob/foo'
    $ replace-in-files --dry-run --string='old' --replacement='new' file.txt

  You can use the same replacement patterns as with `String#replace()`, like `$&`.

  When working with quotes in shell commands, escape them with backslashes:
    $ replace-in-files --string='\"use strict\";' --replacement='\"use strict\";\nrequire(\"module\");' file.js

Real-world use-case: Bumping version number in a file when publishing to npm

The regex should be JavaScript flavor.

API

You can also use this package programmatically:

import replaceInFiles from 'replace-in-files-cli';

// Find and replace
await replaceInFiles('*.js', {
	find: ['old', /version \d+/],
	replacement: 'new'
});

// Transform entire file content
await replaceInFiles('*.js', {
	transform: (content, filePath) => `/* Banner */\n${content}`
});

// Combine find/replace with transform (transform runs after find/replace)
await replaceInFiles('*.js', {
	find: ['old'],
	replacement: 'new', 
	transform: (content, filePath) => `/* ${filePath} */\n${content}`
});

The transform option provides full control over file content:

  • Standalone: Use alone for prepend, append, or complex transformations
  • Combined: Use with find/replacement - transform runs after find/replace operations
  • Parameters: Receives (content, filePath) for context-aware transformations