Skip to content
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

File changes made don't trigger hot reload - WSL2 #73

Open
eblakem opened this issue Nov 6, 2023 · 0 comments
Open

File changes made don't trigger hot reload - WSL2 #73

eblakem opened this issue Nov 6, 2023 · 0 comments

Comments

@eblakem
Copy link

eblakem commented Nov 6, 2023

Thanks so much for your work on this, it is the best.

I came across this issue (not caused by elm-watch) and thought it might be good to have a note of it in the documentation, however it might also be a bit too abstract to overly worry about.

I am on a Windows machine using vscode devcontainers for my development environment. My repository was located in my Windows User's folder (e.g. C:\Users\michael\Repos). My devcontainer Dockerfile is using ubuntu:jammy.

Essentially file changes made on the windows filesystem don't trigger file changes within the devcontainer, which meant hot reloading was not working.

Moving the repository into WSL2 is the solution. There is a warning on the vitejs website that better explains it vitejs.dev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant