-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Hot reloading on file changes in docker no longer working in typescript 4.9.5 #52712
Comments
After upgrading TypeScript to 4.9.5 from which version? |
From 4.8.4 |
Stopped working for us as well. Maybe this is what changed? |
Yeah, we changed the default filesystem watch implementation to one that's generally more efficient. It's possible your OS/FS/etc environment doesn't support this, however. You can set the |
fixedpollinginterval worked fine. |
posting a recap and adding a few extra keywords since it took me a bit to track down this issue from google... for anyone else that ends up here due to an error that looks like:
i believe the new way that file watching works does not work on macos catalina (10.15.x, and possibly below), so the suggestion above was required. to be more explicit: add to your "compilerOptions": {
...
},
"watchOptions": {
"watchFile": "fixedpollinginterval",
}, alternatively you can set the following environment variable: export TSC_WATCHFILE="PriorityPollingInterval" |
Thank you. You saved my day. |
Bug Report
After upgrading to typescript 4.9.5, hot reloading stopped working in a docker environment. In our use case, we are using nestjs with command
nest start xx --watch --tsc
. I saw in the issue linked below that there have been changes to the file system. Is there anything docker/nest/typescript can do to get it working again ?docker/compose#10027
🔎 Search Terms
docker
🕗 Version & Regression Information
After upgrading to typescript 4.9.5
🙁 Actual behavior
Docker no longer detecting file changes
🙂 Expected behavior
Docker should detect file changes
The text was updated successfully, but these errors were encountered: