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
I have used this plugin before and it works great, but I've really struggled to get the hot reload portion of it working in a Docker container.
I have a React + Typescript project that I launch in a container with a bind mount to the local files.
When the container starts, the checker works perfectly. However, when I make a code change, Vite updates properly, but the checker doesn't update. My guess: There are some issues with Vite hot reloading in a Docker container on Windows (the OS of my PC). You have to set the "chokidar" watcher usePolling option to true. I wonder if the same needs to happen here...
Attempt to run a Vite + React + Typescript app with the checker in a Docker container with hot reloading hmr: truewatch: { usePolling: true } on a Windows machine?
Expected behavior
The checker should hot reload on file changes as expected.
Describe the bug
I have used this plugin before and it works great, but I've really struggled to get the hot reload portion of it working in a Docker container.
I have a React + Typescript project that I launch in a container with a bind mount to the local files.
When the container starts, the checker works perfectly. However, when I make a code change, Vite updates properly, but the checker doesn't update. My guess: There are some issues with Vite hot reloading in a Docker container on Windows (the OS of my PC). You have to set the "chokidar" watcher
usePolling
option totrue
. I wonder if the same needs to happen here...Reproduction
Attempt to run a Vite + React + Typescript app with the checker in a Docker container with hot reloading
hmr: true
watch: { usePolling: true }
on a Windows machine?Expected behavior
The checker should hot reload on file changes as expected.
System Info
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: