-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cargo watch
No longer auto reloading since 0.2.25
#430
Comments
My best guess is that line cargo-leptos/src/service/notify.rs Line 98 in b2136f1
ReadDirectoryChangesW API. I don't have Windows to test it out, but could you please add the following code before return and show me the logs here?
log::error!("Notify ignored the event {:?}", event); |
|
Thanks for sharing, my guess was right. I will create a patch for this. |
sabify
added a commit
to sabify/cargo-leptos
that referenced
this issue
Feb 3, 2025
windows isn't specific about the notify event (closes leptos-rs#430)
Could you please check this PR (#432) out and see if it is working? |
Yes, it worked. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since version 0.2.25
cargo-leptos watch
does not automatically recompile the code and restart the server on Windows when it detects changes. It seems like it doesn't detect changes at all. It still works in 0.2.24. The problem still exists in 0.2.27.After some testing, I can confirm it is due to this commit: b900521
@sabify
The text was updated successfully, but these errors were encountered: