How does dev mode work for you in Docker?

[andxbes]

My server is running at the address in the Docker container:
http://test.local . I changed origin:'http://test.local' in the config.

I run npm run dev on the host and it says it's started.

VITE v6.3.3 ready in 246 ms

➜ Local: http://localhost:3000/
➜ Network: use --host to expose
➜ press h + enter to show help

I navigate to http://localhost:3000/ and get HTTP ERROR 404

[andxbes]

I edit the config to this, and the Vit server starts displaying WordPress pages, but it doesn't track file changes or recompile the CSS. Changes are only made using npm run build.

`export default defineConfig(({ command }) => {
const isBuild = command === 'build';

return {
    base: isBuild ? '/wp-content/themes/tailpress/dist/' : '/', 
    server: {
        port: 3000,
        host: true, 
        cors: true,
        allowedHosts: ['test.local', 'localhost', '192.168.1.60', '192.168.48.1'], 
        proxy: {
            '/': 'http://test.local',
        }
    },
    build: {
        manifest: true,
        outDir: 'dist',
        rollupOptions: {
            input: [
                'resources/js/app.js',
                'resources/css/app.css',
                'resources/css/editor-style.css'
            ],
        },
    },
    plugins: [
        tailwindcss(),
    ],
}

});`

[yudin-s]

npm run dev working but no rebuild on file edits in Docker is usually a file-watch propagation issue, not Vite routing.

In this setup, the common fix is:

1. Ensure theme source directory is bind-mounted into the container path you actually edit.
2. Force polling watchers for Docker/VM filesystems.

Example env for dev:

CHOKIDAR_USEPOLLING=1
CHOKIDAR_INTERVAL=250
WATCHPACK_POLLING=true

Also keep Vite reachable from containerized WP:

• server.host = true
• server.hmr.host set to the host/IP visible from container (not always localhost)
• verify container can reach http://<hmr-host>:3000

404 on localhost:3000 is expected if you browse Vite root directly while your app is served through WordPress proxy; the key signal is whether HMR websocket connects and CSS changes trigger rebuild events.

If this solved it, please mark the answer so others can find it faster.

[andxbes]

Thank you. This is how I solved the problem with working in a Docker container.

4eb656c