Rolldown Vite issue with HMR

[Hardel-DW]

Which project does this relate to?

Router

Describe the bug

Hot Module Replacement (HMR) is not functioning correctly when using Vite with Rolldown. The issue specifically affects pages in the "routes" folder, while components outside of route files work but experience slow HMR performance.

Your Example Website or App

https://github.com/Hardel-DW/tanstack-bug-hmr

Steps to Reproduce the Bug or Issue

1. Set up a project with Vite + Rolldown "vite": "npm:rolldown-vite@latest"
2. Create routes in the routes folder

import { createFileRoute } from "@tanstack/react-router";

export const Route = createFileRoute("/$lang/hello")({
    component: Page,
});

function Page() {
    return (
        <div>
            Hello world
        </div>
    );
}

4. Make changes to route components. E.g change "Hello world" -> "Hello Bug"
5. Observe that HMR does not trigger. (But the console detect HMR)
6. Make changes to components outside routes folder
7. Observe slow HMR performance

Expected behavior

HMR should work normally for all files including those in the routes folder
HMR should have fast refresh times similar to standard Vite

Screenshots or Videos

2025-09-02_13-22-57.mp4

Platform

• Router: @tanstack/react-router": "^1.131.31
• OS: Windows
• Browser: Chrome, Firefox and Zen
• Browser Version: 139 For Chrome
• Bundler: Vite Rolldown
• Bundler Version: "vite": "npm:rolldown-vite@latest"

Additional context

It's annoying because we don't know where it comes from when it appears.
In my case, I migrated from NextJS to TanStack Router, and I was using vite rolldown, which worked with NextJS. But that caused me problems here but it took me a long time to understand that it was the roll down that was the problem..

[nandcello]

I'm on rolldown-vite@7.1.8 & tanstack-router@1.131.36 and I'm getting the same issue minus the HMR perf probs on components outside routes/ folder; those work just fine for me.

[TheAlexLichter]

Raised in vitejs/vite-plugin-react#871. Feel free to raise it directly in rolldown-vite next time (otherwise it is hard for use to track/find) 👍

[nandcello]

fix for this has been merged via this PR

[TheAlexLichter]

A fix has been released in plugin-react@5.0.3