codemod@latest not actually running react/19/migration-recipe

[jbrz]

Issue Description

• Bug in Codemod CLI

Having fiddled with the settings and the run environment, this seems like it must surely be a bug, but I'm happy to be told otherwise - just not sure how a relatively-new-migration-version codemod could be legacy and only able to run on a far-in-the-past version.

Steps to Reproduce

1. npx codemod@latest react/19/migration-recipe
2. question life

Actual Results

Need to install the following packages:
codemod@1.0.1
Ok to proceed? (y) y

[1/2] 🔍 Resolving package from registry: https://app.codemod.com ...
⚠️ Package react/19/migration-recipe is legacy
[2/2] 🏁 Running codemod: react/19/migration-recipe
Need to install the following packages:
codemod@0.18.9
Ok to proceed? (y) y
╭──────────────────────────────────────────────╮
│                                              │
│       Update available 0.18.9 > 1.0.1        │
│                                              │
│   Run "npm i -g codemod@latest" to upgrade   │
│                                              │
╰──────────────────────────────────────────────╯
✔ Successfully downloaded "react/19/migration-recipe" from the registry.

Expected Results

• Resolving package from registry
• Running codemod: react/19/migration-recipe
• "successfully downloaded[/fetched]..."
• executed codemod

Technical details

• Codemod CLI version: ???
• Node.js versions: 18.20.8, 20.19.4, 22.17.1, 24.4.1

[mohebifar]

Hey @jbrz , thanks for reporting this issue. Do you not see any changes applied by the codemod?

I understand the messages that get printed about versions are a bit confusing. We'll work on improving that. The thing is react codemods are jscodeshift codemods that we continue to support in maintenance mode, but in order to run them, behind the scenes, we need to reroute it to npx codemod@legacy.

If the codemod is actually doing nothing, then there might be an issue there.

[jbrz]

@mohebifar Unfortunately, we'd already done most of the updates we knew were going to be problematic, so the codemod isn't ending up modifying anything—essentially 'as-expected', sorry! But it does appear to be looking through the whole project structure and completing its checks.

It just seemed bizarre if not concerning that despite trying to use a 1.x.x version of codemod it was essentially punting us back in time to run the react recipe(s). But if that's just an artifact of the substructure doing the work, I think you can close this as nofix—though clarification in the CLI might be at least helpful for future folks.