You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because of ReactPy's granular core abstractions it should be possible to run ReactPy client-side with Pyodide or PyScript. Using ReactPy instead of a solution that relies on a transpiler could have some advantages:
Components can be run client-side or server-side without any changes
No need to fiddle with weird bugs caused by back transpilation
ReactPy's client already uses React to render its JSON serializable VDOM into an actual view, so if the DOM representation were already client-side (as it would be with Pyodide) it should be trivial to send that representation to React directly rather than over a websocket.
Activity
rmorshea commentedon Apr 18, 2021
Looks like #245 has been fixed. Maybe we can try this out?
[-]Integrate iDOM with Pyodide[/-][+]Integrate IDOM with Pyodide[/+][-]Integrate IDOM with Pyodide[/-][+]Integrate ReactPy with Pyodide[/+][-]Integrate ReactPy with Pyodide[/-][+]Support client-side components (with Pyodide)[/+]rmorshea commentedon Jun 19, 2023
Apparently NextJS's router manages to switch between client/server components fluidly.
[-]Support client-side components (with Pyodide)[/-][+]Client Side Python Components[/+]