React ClientOnly stucks on fallback in Chrome 53

[teukuridho]

Reproduction:

1. Init vike.js pnpm create @batijs/app --react --express
2. Install vike-react
3. Modify Counter component like this

export { Page }

import { Counter } from './Counter'
import { ClientOnly } from 'vike-react/ClientOnly';

function Page() {
 return (
   <>
     <h1>Welcome</h1>
     This page is:
     <ul>
       <li>Rendered to HTML.</li>
       <li>
         Interactive.
         <ClientOnly 
           fallback={<p>Loading</p>}
           load={async () => Counter}
         >
           {(Component) => <Component/>}
         </ClientOnly>
       </li>
     </ul>
   </>
 )
}

4. Run on chrome 53, ClientOnly stucks on fallback, no errors or warnings in console
   

how do I resolve this? thank you

[brillout]

Chrome 53 was released in 2016, any reason you want to support a browser version that old?

…

On Sat 11. May 2024 at 16:55, teukuridho ***@***.***> wrote: Reproduction: 1. Init vike.js pnpm create @batijs/app --react --express 2. Install vike-react 3. Modify Counter component like this export { Page } import { Counter } from './Counter' import { ClientOnly } from 'vike-react/ClientOnly'; function Page() { return ( <> <h1>Welcome</h1> This page is: <ul> <li>Rendered to HTML.</li> <li> Interactive. <ClientOnly fallback={<p>Loading</p>} load={async () => Counter} > {(Component) => <Component/>} </ClientOnly> </li> </ul> </> ) } 3. Run on chrome 53, ClientOnly stucks on fallback ***@***.*** (view on web) <https://github.com/vikejs/vike/assets/51054737/95dd6e6c-bc52-4ec2-a768-f9daa1d02dc5> how do I resolve this? thank you — Reply to this email directly, view it on GitHub <#1638>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHVQRT4J6G7TX5OJIQQXDLZBYWONAVCNFSM6AAAAABHR7UZGWVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZWGY2DMOJTHE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[teukuridho]

yes, I need my app to run on a LG WebOS tv, the latest chrome available for it is chrome 53 sadly, even after firmware upgrade...

[brillout]

In general, Vike doesn’t support browsers that old. But feel free to dig and report back your findings; maybe there is a straightforward way to support Chrome 53.