Let's go deeper, try an official Vue app template and tell me if hot reload works after changing App.vue file: $ npm install -g vue-cli $ vue init webpack my-project $ cd my-project $ npm install $ npm run dev. "docker-compose run --rm -p 4000:8080 node npm run serve". I don't really understand why, the configuration seems ok to me, maybe my "start" command which is not good ? Docker is a containerization tool used to speed up the development and deployment processes. Docker and Webpack hot reload not working - Stack Overflow Now that we are inside the Linux environment, we can start doing some house keeping by first deleting the node_modules folder and the package-lock.json file. Hot Module Replacement | Laravel Mix Documentation The problem with Laravel Sail is, HMR does not work with its default configuration. We create our Dockerfile with these characteristics: it should run node with a command (yarn run start); it should create a /usr/src/app working directory; it should expose its 3000 port (Webpack Dev Server port). web: build: context: . Getting started with Vite is simple. Option 3: Express with webpack-dev-middleware (client & server) If you're working with microservices, Docker makes it much easier to link together small, independent services. During development, I usually have a website with a web frameowork at localhost:8080 and have webpack do it's magic npm run dev serving app.js at localhost:3000/app.js. So first of all, we need to expose a new port of the Laravel Docker container for the HMR to communicate with the browser. Including hot reload on save. Npm Run Dev: Modify Vue Webpack Template Dev Server to use ... - GitHub Informations: Laravel: v8.41.. PHP: PHP v8.0.5. This post details my initial journey with running my first Docker container based Node.js application under Windows 10 - as well as the challenges encountered with live reload via nodemon during the journey, and how I got everything working well enough in the end. Hot Module Reloading with Next.js Docker development environment in 4 ... 3) Get both of them running with a docker-compose file.