3 ms·
That's been my experience, as well. I got everything working because I'm very familiar with Vue, but I did end up removing a lot of TypeScript from my app just
by FinalBriefing 5y ago
That's been my experience, as well. I got everything working because I'm very familiar with Vue, but I did end up removing a lot of TypeScript from my app just to make it all easier. Luckily, Vue makes it easy to mix and match JS and TS (for better or for worse).
- adevx 5y agoI jumped on the React bandwagon because I didn't like the Typescript support in Vue 2, and did not see much improvements for V3. Vscode Vetur was slow and unable to do full typechecking in Vue files. Much of my code was based on Vue Class Components, which was not going to be compatible with the new API. Vuex did not seem to be going in the Typescript direction either. A bit sad if you consider Vue 3 is written in Typescript.
- rk06 5y agoVuex is going in direction of pinia. While Vuex has a v3 compatible build, it is there to ease migration, not as recommended for new vue 3 users
- zigomir 5y agoTS support has been improved dramatically with volar VSC extension and vue-tsc CLI tool. When that was released (I’d need to check when but in 2021 or even late 2020) my React FOMO disappeared as I get full TS support in script and template tags. Composition api + VueUse are wonderful together. I’ve been lucky to start fresh with vue 3 mid 2020 (in beta?). But I and can understand frustration to migrate. Having said that, I think it’s totally worth it.