-
Notifications
You must be signed in to change notification settings - Fork 12.8k
tsc -b --watch emits unchanged js on each compilation round #35340
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
Comments
This is working as intended.. We do not track if change in file will not result in its output js file or not. We emit it irrespectively. |
@sheetalkamat, It's may be OK for this particular file, but all other js files among all projects, which are linked up through project dependency graph, are also emitted despite whether they depends on changed file or not. For example if I have project B which depends on project A, and I change one file in A, all files from A and all files from B will be emitted How it supposed to be integrated to any dev-build pipeline which performance usually heavily depends on amount of changed files ? By the way the problem appears only with |
This issue has been marked 'Working as Intended' and has seen no recent activity. It has been automatically closed for house-keeping purposes. |
Just for history, webpack was triggered by setting timestamps on all output files during project invalidation step, so there is nothing wrong with emit. |
TypeScript Version: 3.7.2
Search Terms: project references
Code
Expected behavior: each recompilation write only changed js files to output
Actual behavior: each recompilation write all js files to output in all projects
As far as I understand, files should be written by
writeFileIfUpdated
, but it never invoked. Instead this function calledRelated Issues: probably regression of #29927
Steps to reproduce:
npm run init
npm run tsc:watch
and wait till build will be completednpm start
number
toany
, which should not lead to changes in corresponding js fileThe text was updated successfully, but these errors were encountered: