.tsbuildinfo not ignored when incremental is false. #62565
Description
🔎 Search Terms
.tsbuildinfo
🕗 Version & Regression Information
This changed between versions 5.6 and 5.6.3
⏯ Playground Link
No response
💻 Code
// Your code here🙁 Actual behavior
In 5.6, .tsbuildinfo was changed to always emit, but this was a breaking change. Even with incremental and composite set to false, the .tsbuildinfo is emitted, and prevents the project from recompiling until it is deleted. There is also no option to disable emitting the file to avoid it's side effects. This has led to several (mine, collab) NPM packages being published without latest code updates.
🙂 Expected behavior
- When incremental and composite is false, all files should be recompiled regardless of the existence of a tsbuildinfo file. AKA default build behavior should produce a clean build regardless of file state. (Current workaround is to run clean first but this does not always remove all files)
- It should be possible to disable emitting the tsbuildinfo to avoid polluting the dist package for production builds. (current workaround is to either put it in a random folder or add an extra build step to delete the file before publish, or copy in a .npmignore, however this adds extra build complexity)
Additional information about the issue
Closest ticket I could find was this issue which was marked as working as intended, but the default behavior changing, and options to avoid that default behavior are two completely separate things. Even if the default emit is intended, the use case to have an option to disable that is also valid.