Some codemod commands in the README.md cause errors and can't be run

[shsatovg]

Overview

Some codemod commands in README.md cause errors and can't be run.
The commands that cause errors include pure-render-mixin, error-boundaries, and findDOMNode. For more details, please refer to the section ### Codemod Registry Status.

How to Reproduce the Error and Examples

This is how to reproduce the error and examples:

$ npx codemod react/pure-render-mixin --target src

× Fetching "react/pure-render-mixin"...
The specified command or codemod name could not be recognized.
To view available commands, execute "codemod --help".
To see a list of existing codemods, run "codemod search" or "codemod list" with a query representing the codemod you are looking for.

Why the Error Happens

The codemod command might not be listed in the Codemod Registry.

Codemod Registry Status

Here’s a simple table showing if each codemod is in the registry:

Codemod Name	Is it in the Registry?
remove-context-provider	Yes
remove-forward-ref	Yes
use-context-hook	Yes
replace-act-import	Yes
replace-string-ref	Yes
replace-use-form-state	Yes
replace-reactdom-render	Yes
create-element-to-jsx	Yes
error-boundaries	No
findDOMNode	No
manual-bind-to-arrow	No
pure-component	No
pure-render-mixin	No
React-PropTypes-to-prop-types	No
rename-unsafe-lifecycles	Yes
react-to-react-dom	No
React-DOM-to-react-dom-factories	No
ReactNative-View-propTypes	No
update-react-imports	Yes

What We Want

Please add the codemods that are not in the registry. If you can't do that, please change the document to show which ones are missing.

References

Related past ISSUES include:

• react/update-react-imports could not be recognized when running #326
• create-element-to-jsx could not be recognized #327
• Error: react/rename-unsafe-lifecycles command could not be recognized #329