fi3ework/vite-plugin-checker

why (Vue3 + vue-tsc) so bad compaired to (React + TypeScript ) ?

moHaHa opened this issue · 3 comments

moHaHa commented

Describe the bug

(Vue3 + vue-tsc) vs (React + TypeScript)

Reproduction

(Vue3 + vue-tsc) vs (React + TypeScript)

Expected behavior

(Vue3 + vue-tsc) vs (React + TypeScript)

System Info

(Vue3 + vue-tsc) vs  (React + TypeScript)

Additional context

(Vue3 + vue-tsc) vs (React + TypeScript)

Validations

  • Read the docs.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
fi3ework commented

TypeScript supports React internally, which vue does not. vue-tsc did a lot of great work to make type check works for vue combined with TypeScript. Please keep nice in the community.

  • 👍1
moHaHa commented

TypeScript supports React internally, which vue does not. vue-tsc did a lot of great work to make type check works for vue combined with TypeScript. Please keep nice in the community.

ok thanks for your answer ,
I'm just asking becaouse I worked with vue for 2 years without TS , and only 3 months of working with react and TS made me switch to react
when I back to make some code and refactor with Vue I had many issues with ts and type checkeing and not that easy to work , I can refactor project fo 8 modules each one with 4 large pages in react TS , but when it's come to vue I'm scared to refactor only 5 large pages !!