Solution builder not detecting out of date compiler options #62035

🔎 Search Terms

"solution builder cache", "tsbuildinfo cache", "compiler options change build"

🕗 Version & Regression Information

n/a

⏯ Playground Link

n/a

💻 Code

n/a

🙁 Actual behavior

1. In a project using references, suppose you have a tsconfig.json specifying any random option (e.g., skipLibCheck: true).
2. Run a build using tsc --build ./tsconfig.json.
3. See output.
4. Run the build again, this time programmatically using createSolutionBuilder and override one compiler option via getParsedCommandLine in the builder host (e.g., skipLibCheck: false).
5. Build will be skipped as the builder sees project files are not out of date, but fails to detect that compiler options are not the same used during the last build. We get the same output of the previous run.
6. Cleaning up .tsbuildinfo files and running the build programmatically again work as expected. New output is different from the first one.

🙂 Expected behavior

I would expect the builder to detect that new compiler options are different from the last used and re-build that project.

Additional information about the issue

I narrowed down the issue to ./src/compiler/tsbuildPublic.ts - Line 1606

Basically, there is where UpToDateStatusType.OutOfDateOptions is reported, but current compiler options are not being compared with the ones from the relative tsbuildinfo file.

Manually changing the tsconfig.json file works because the timestamp of the file changes and not because options are different.

I discovered this while creating a script to address #30511

Note: I would be happy to open a PR