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

code-migrator

v2.0.0

Published

Create code migration tool for your tool/library/framework.

Readme

code-migrator Build Status

This library help to create code migration tool.

gif

This library help to create migration tool for your library/framework/tool.

  • This library aim to provide command line interface for migration
  • This library help to run migration scripts
  • This library does not provide migration scripts
    • You have to write migration script
    • You choose codemod tool by own
    • Your migration script must not depended on this library

codemod tools

You have to write migration scripts using following codemod tools.

code-migrator is a launcher library for the above tools.

Install

Install with npm:

npm install code-migrator

Requirements

  • Your library/framework/tool should follow Semantic Versioning
  • You have to prepare migration scripts

Usage

Define MigrationList

module.exports = {
    scripts: [
        {
            name: "use-strict",
            // absolute path for codemod scripts
            filePath: require.resolve("./scripts/use-strict")
        }
    ],
    versions: [
        // 0.x.x -> 1.0.0 apply "use-strict"
        {
            version: "1.0.0",
            scripts: ["use-strict"]
        },
        // 1.0.0 -> 2.0.0 does not apply anything
        {
            version: "2.0.0",
            scripts: []
        },
        {
            version: "3.0.0",
            scripts: []
        }
    ]
};

Example:

const { CodeMigrator } = require("code-migrator");
const meow = require("meow");

const cli = meow(
    `
    Usage
      $ code-migration-example <input>

    Options:
      --dry-run Enable dry run mode

    Examples
      $ code-migration-example "src/**/*.js"
`,
    {
        flags: {
            dryRun: {
                type: "boolean"
            }
        }
    }
);

const migrator = new CodeMigrator({
    moduleName: "test-module", // <= target npm module name if needed
    migrationList: require("../migrations"), // load migration list
    binCreator: ({ script, filePathList }) => {
        // migration script is executed by jscodeshift
        const binArgs = cli.flags.dryRun ? ["--dry"] : [];
        return {
            binPath: require.resolve(".bin/jscodeshift"),
            binArgs: binArgs.concat(["-t", script.filePath]).concat(filePathList)
        };
    }
});
migrator
    .run({
        filePatterns: cli.input
    })
    .then(() => {
        console.log("Done");
    })
    .catch(error => {
        console.error(error);
    });

For more details, see examples/

How to write unit test?

Code Migrator use Inquirer.js for building interactive interface. It is useful, but it is difficult to test.

You can run Code Migrator with non-interactive mode.

run(options: CodeMigratorRunOption)

If you set all defaultValue option, you can run code without interactive prompt.

const migrationList: MigrationList = require("./fixtures/scripts/migrations.js");
const codeMigrator = new CodeMigrator({
    migrationList: migrationList,
    moduleName: "test",
    binCreator: ({ script, filePathList }) => {
        return {
            binPath: require.resolve(".bin/jscodeshift"),
            binArgs: ["--dry", "-t", script.filePath].concat(filePathList)
        };
    }
});
codeMigrator
    .run({
        force: true,
        defaultValue: {
            currentVersion: "0.1.0",
            nextVersion: "3.0.0",
            files: [path.join(__dirname, "fixtures/scripts/src/**/*.js")]
        }
    });

runScripts(options: RunScriptsOptions)

runScripts is non-interactive mode by default.

const migrationList: MigrationList = require("./fixtures/scripts/migrations.js");
const codeMigrator = new CodeMigrator({
    migrationList: migrationList,
    moduleName: "test",
    binCreator: ({ script, filePathList }) => {
        return {
            binPath: require.resolve(".bin/jscodeshift"),
            binArgs: ["--dry", "-t", script.filePath].concat(filePathList)
        };
    }
});
codeMigrator.runScripts({
    force: true,
    scripts: migrationList.scripts,
    files: [path.join(__dirname, "/fixtures/scripts/src/**/*.js")]
});

User

Following migration tools use code-migrator.

Changelog

See Releases page.

Running tests

Install devDependencies and Run npm test:

npm i -d && npm test

Contributing

Pull requests and stars are always welcome.

For bugs and feature requests, please create an issue.

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D

Author

License

MIT © azu

Acknowledgment

This library is based on ava-codemods.