Why do we need --force for vue-tsc?

[jemdiggity]

Vue-create by default uses the following for the type-check script:
"type-check": "vue-tsc --build --force",
Using --force is obviously a low slower than no using it. It takes about 12 seconds on my machine for the project I'm working on.
Is there a reason why this flag needs to be included? Can't we just check out of date files?
Thanks in advance.

[qnp]

Related question, why vue-tsc --build --force is the default command instead of vue-tsc --noEmit which is recommended in the vue-tsc documentation ?

[bokub]

Looks like the documentation has been changed. It now recommends using vue-tsc --noEmit

[barry166]

For current create-vue templates, the script is now vue-tsc --build without --force. The generated tsconfigs also set tsBuildInfoFile under node_modules/.tmp, so TypeScript build mode can reuse incremental state instead of doing a forced full rebuild every time.

So yes, you can drop --force if your project has normal tsconfig.*.json build references and the .tsbuildinfo files are preserved between runs. Keep --force only for CI/clean-check situations where you intentionally want to ignore stale incremental state. vue-tsc --noEmit is fine for a single tsconfig, but create-vue uses build mode because the app/node/test configs are separate projects.

[bokub]

Perfect, thank you!