Returning of jsx elements (functions) in loader and reading them from loader data returns undefined

[saverchenko2002]

Reproduction

https://stackblitz.com/edit/github-xydx43ei?file=app%2Froutes%2Fhome.tsx

System Info

System:
    OS: Windows 10 10.0.19045
    CPU: (4) x64 Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
    Memory: 4.04 GB / 15.95 GB
  Binaries:
    Node: 22.14.0 - C:\Program Files\nodejs\node.EXE    
    Yarn: 1.22.22 - ~\AppData\Roaming\npm\yarn.CMD      
    npm: 11.5.2 - C:\Program Files\nodejs\npm.CMD       
  Browsers:
    Chrome: 140.0.7339.128
    Edge: Chromium (140.0.3485.54)
    Internet Explorer: 11.0.19041.5794
  npmPackages:
    @react-router/dev: ^7.7.1 => 7.8.2
    @react-router/node: ^7.7.1 => 7.8.2
    @react-router/serve: ^7.7.1 => 7.8.2
    react-router: ^7.7.1 => 7.8.2
    vite: ^6.3.3 => 6.3.5

Used Package Manager

npm

Expected Behavior

I want to see my passed component being rendered instead of undefined without compiler error

Actual Behavior

After deserealizing from loader data becomes undefined
Affecting React.ComponentType and React.ReactNode

[timdorr]

Functions are not a serializable type to return from a loader. You should use some other means to communicate which component you want your route to use.

[GabenGar]

Very unlikely it's not planned, because returning react server components from loaders was the killer feature advertised in preview blog post. And returning react components from server responses is a killer feature of React 19 (the version specified in repro).