I have been playing around with nestjs microservices and I encountered an issue when using containerized services. Standalone nestjs applications are usually configured with a file watcher on dev mode( i think it uses ts-node under the hood ). The issue I am facing is that, despite my local environment clearly being mounted to the container( i ssh into the containers so i actually see changes being reflected) , the watcher refuses the restart the service on file changes.I tried to update the[b] watch [/b]attribute of ts-config.json in the root application to true, and also passed CHOKIDAR_USEPOLLING=true as a global env variable in my docker-compose file for the service, all to no avail.I think the issue lies with the WSL in Windows OS(i use docker for Windows).If anyone has a workaround on this please kindly direct me. Because I had to improvise by restarting each container anytime I make any file changes ..which is fucking frustrating