@gaearon I think you are best reviewer as a original author.
Please feel free to feedback when if you have a plenty time! 😄

Not sure why the replace-fork CI fails for non-reconciler stuff like this. Looks like our script is broken.

@bvaughn Hello Brian👋 This is Sunday so could you have plenty rest time? 😀

I don't know this CI background though, looks like there is diff on git between original and fork.
git diff --quiet || (echo "Reconciler forks are not the same! Run yarn replace-fork. Or, if this was intentional, disable this CI check." && false)
Kind of CI task is not appear general development, feels like rare setup React repo specific.
Anyway I'm going to find what does job do tracking git history. 👨‍💻

Running yarn replace-fork on this branch results in a bunch of bogus replacements: changing import paths in several .old.js files to reference .new.js modules. This does not happen on HEAD of main branch though.

I rebased your branch on main and tried re-running and it still fails. Weird.

It's caused by an ESLint error causing the replace-fork script to silently crash. (The replace-fork script relies on ESLint to fix the imports.)

Try running yarn linc on this branch and you'll see the error:

Error: Failed to load config "react-app" to extend from.
Referenced from: fixtures/blocks/package.json

Now that #22156 has landed, if you rebase on HEAD of main branch you'll see the underlying error here in CI (or when you run yarn replace-fork)

After rebase and push for apply this fix,

• Yarn replace-fork should not silently error #22156

Still failed but showing ESLint message Error: Failed to load config "react-app" to extend from. with exit code 1.
It works! 😄

This pull request has been automatically marked as stale. If this pull request is still relevant, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize reviewing it yet. Your contribution is very much appreciated.

Closing this pull request after a prolonged period of inactivity. If this issue is still present in the latest release, please ask for this pull request to be reopened. Thank you!