Problems with hot reload?

[jgutierrez2]

Anyone else having trouble with hot reloading on .py file changes?

It's always worked great but over the last few weeks, across a few versions (including the recent 0.7.12), saving changes to a .py file will trigger a compile and refresh the browser page, but changes I've made to the UI are not reflected. Exiting and re-running "reflex run" is the only way I've been able to get changes reflected.

[adhami3310]

i haven't personally noticed it, is it consistent? over different projects?

[larsblumberg]

I'm also currently struggling with hot reload not working. I can see in the logs that reflex catches file changes but the components wouldn't rerender according to the changes.

[adhami3310]

you can also upgrade bun but i haven't seen much related to fs watch files in the past two versions

[larsblumberg]

can you install node and try again?

Hot-reload works with npm run dev even when turbopack is disabled

you can also upgrade bun but i haven't seen much related to fs watch files in the past two versions

Reflex currently installs bun in version 1.2.13

> /app/.web# /root/.local/share/reflex/bun/bin/bun -v
1.2.13

With

> curl -fsSL https://bun.sh/install | bash
> source ~/.bashrc  # reload changes to $PATH
> bun -v
1.2.15
> bun run dev

hot-reload does work, also here with turbopack disabled.

So maybe it's just a matter of having reflex installing latest bun version?

[larsblumberg]

Out of curiosity, why isn't next --turbopack the default for reflex?

[adhami3310]

interesting, i might bump up the minimum dependencies (bun) for reflex in next release

in any case, if you're making a docker, you should install bun and node yourself in the system package

[adhami3310]

why isn't next --turbopack the default for reflex?

there's just more bugs in turbopack than in webpack, once they make progress on specific bugs we're hitting we can consider that

https://github.com/vercel/next.js/issues?q=is%3Aissue%20state%3Aopen%20label%3ATurbopack%20type%3ABug

https://github.com/vercel/next.js/issues?q=is%3Aissue%20state%3Aopen%20type%3ABug%20label%3AWebpack

[ghost]

I mean did u try using python virtual env ?, cuz it worked for me 😊

[jamesalphanome]

I am getting the similar issue in 0.7.13

[nengelmann]

I got this issue fixed on my side by upgrading to uvicorn>=0.25.0.

pip install 'uvicorn>=0.25.0'

See also the comments in #5351.

[uuleejie-olo]

I met the same thing. My reflex version is 0.7.14

[larsblumberg]

I met the same thing. My reflex version is 0.7.14

Try enabling turbopack, that fixed it for me. Make sure to delete the .web directory before starting your app, once you changed the turbopack setting. See my comments above.

[adhami3310]

please let us know if those issues still persist in 0.8.0

[JaimeTavera]

I don't know if this is the right place but since I recently updated to 0.8.2, every time I save a change, the app gets reload and changes are implemented in the app, but also I get the next error message:

App running at: http://localhost:3000/
Backend running at: http://0.0.0.0:8000
[21:50:29] Compiling: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 27/27 0:00:00
[Reflex Frontend Exception]
 Error:  No module update found for route routes/._index
    at http://localhost:3000/@id/__x00__virtual:react-router/hmr-runtime:476:15

[JaimeTavera]

I found in Issues a sugestion of updating node to 24.4.0 ad it worked for me too.

[neyec]

Hi, I'm using 0.8.15 and get the same error.

[Reflex Frontend Exception]
 Error:  No module update found for route routes/._index
Error:  No module update found for route routes/._index
    at http://localhost:3000/@id/__x00__virtual:react-router/hmr-runtime:441:25

[neyec]

Updating to node 25 seems to have fixed it, as mentioned by @JaimeTavera.

[neyec]

Nope, errors still there.

[LuizSuzana]

Hello, I found the same error with reflex 0.8.21 and 0.8.22:

[Reflex Frontend Exception]
 Error:  No module update found for route routes/._index
Error:  No module update found for route routes/._index
    at http://localhost:3000/@id/__x00__virtual:react-router/hmr-runtime:442:25

[masenf]

the "No module update found for route" is #5545

Safe to ignore, doesn't impact functionality. We may suppress this message in a future release, since it isn't valuable and often is red herring

[adlee-zag]

Still a problem on reflex 0.9.2—no errors but no hot reloading either.