Version

3.2.19

Reproduction link

sfc.vuejs.org/

Steps to reproduce

const testBool = ref(true) testBool.value = 1

What is expected?

App expected to stop rendering, and inform us of error. npm run serve - expected to inform that there is error.

What is actually happening?

App working as if nothing happens. npm run serve - informs that No issues found.

Something strange happened - previous days vue stopped compile on any TS error. It was the way it should behave. Now I've discovered new behaviour - many errors ignored. Аlso see https://github.com/vuejs/vue-next/issues/4710

Mr. @posva closed that previous issue stating that - t would be a huge pain for most users if any TS error prevented the page from rendering by default. But I think that huge pain should be when errors go to production.

In case @posva is right and not all TS errors should cause vue stop working - then I would like a list of such errors.

Duplicate of #4710

Locking to prevent two parallel conversations