-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
tsc --watch emits all files even when they have not changed #29927
Comments
My apologies, it seems this only happens when you save a Can you confirm this is the expected behavior when working with |
This seems to be result of fact that there is no |
Seeing a similar regression here when doing a composite build. I don't have the When we change a single tsx file, everything is re-emitted into the outDir and this really makes webpack run slowly. Not sure if this is related of if I should raise a separate issue. |
@ravenscar please file separate issue with more details on how to repro this for us to be able to investigate this. Since your project doesn't use |
If you check this project https://github.com/Microsoft/TypeScript-Node-Starter.git Then "npm run debug" You will see that "tsc -w" and "nodemon" are interacting and looping I am having this issue and it is very painful because my app has 74 TS files, so when I do "npm run debug" it restarts 74 times! This is the logging:
|
A regression of #3113 / #6937
TypeScript Version: 3.4.0-dev.20190215
Search Terms: tsc --watch writing to disk too often
TypeScript is writing all files to disk regardless if the contents of those files have changed or not. This is fine on startup, but when using
--watch
it still behaves this way even when only one file changes. This causes two problems:nodemon
To Reproduce:
First create some files:
Then run
nodemon server.js
, then re-saveexample.ts
with no changes.Expected behavior:
Only files that have changed should write to disk.
Actual behavior:
All files write to disk.
Related Issues: Seems to be a regression of #3113 / #6937
The text was updated successfully, but these errors were encountered: