Switching to plugin-react-oxc triggers "$RefreshReg$ is not defined" errors

[blixt]

Related plugins

• plugin-react

• plugin-react-swc

• plugin-react-oxc

Describe the bug

Switching from the normal @vitejs/plugin-react in vite.config.ts to the @vitejs/plugin-react-oxc plugin and not changing anything else makes the code in dev/watch mode crash with Uncaught ReferenceError: $RefreshReg$ is not defined if you're using modules from a different context than the main frame (e.g. a Worker). If I look at the code that triggered it, it's usually something like this:

export const MODULE_TYPE_TO_DOMAIN = {
    something: "SomethingElse",
    // ...
};
export const MODULE_DOMAIN_TO_TYPE = swapKeysAndValues(MODULE_TYPE_TO_DOMAIN);
_c = MODULE_DOMAIN_TO_TYPE;
// ...
var _c;
$RefreshReg$(_c, "MODULE_DOMAIN_TO_TYPE");

So that $RefreshReg$ is not available inside a Worker. Which makes sense. What doesn't make sense is that the plugin is trying to consider the MODULE_DOMAIN_TO_TYPE value a component.

Reproduction

N/A

Steps to reproduce

I tried to create a reproduction on StackBlitz but it didn't work to set up the oxc versions of Vite+Rolldown+vite-plugin-react with overrides for Vite.

The repro would be to import a shared library module from a Worker.

System Info

System:
    OS: macOS 15.5
    CPU: (16) arm64 Apple M3 Max
    Memory: 2.49 GB / 128.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.2.0 - /opt/homebrew/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 11.3.0 - /opt/homebrew/bin/npm
    bun: 1.2.5 - ~/.bun/bin/bun
  Browsers:
    Chrome: 137.0.7151.119
    Safari: 18.5

Used Package Manager

bun

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[hi-ogawa]

You don't need to use stackblitz for reproduction and having a repo is also fine for us.

[AntonOfTheWoods]

@hi-ogawa , I'm also getting this but can't find a way to reproduce in a minimal setup. Though open source, my main project is utterly inappropriate for this, as it would require about 2hrs setup on your end. Again, it works fine with the new (7.0.0) rolldown-vite and @vitejs/plugin-react but not with @vitejs/plugin-react-oxc. I guess someone will work out how to repro at some point...

[github-actions]

Hello @blixt. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with need reproduction will be closed if they have no activity within 3 days.

[blixt]

Ok here's a minimal reproduction.

All the info was in the original issue, I just had to create a project that uses a non-React type inside of a Worker and the oxc version of the plugin tries to register that type to HMR as if it was a React component, which crashes because React isn't even running inside of a Worker.

https://github.com/blixt/vite-plugin-react-oxc-issue-514