[alex_marchant]

I hear you, we use this at work and this rings true to our experience as well. One thing though is recently we've started experimenting with typescript? Have you used that? I find that you have to jump through hoops to get typescript and Vue to work together. Looking forward to a form of Vue with better support there.

[rolleiflex]

Yes, I'm using Typescript with Vue. As long as you accept that Typescript is an addition to JS, that is, most of the things you work on will not have Typescript on their own, you can 'gate' it to your parts (i.e. enforce and assert types on your boundaries) and have no problems with it.

It's only when people think of Typescript as a new language where everything must have types things start to go wrong — Javascript won't ever be that. There'll always be a tiny but super useful library from 2004 which has its jQuery dependency removed just 6 months ago, and won't ever get Typescript support, and you have to use it — and if you're a purist that's going to spoil your lunch.

Don't be a purist — a project using Typescript at 50% of its codebase is vastly better than one that uses it at 0%, even if all its asserts are :any's.

[alex_marchant]

Vue is the backbone of our apps, not a small jquery library, good prop types and such is key to day to day work IMO.

[furicane]

I've been using vue, nuxt and typescript without any issues so far (6 months with TS though). It's not vue that's at fault for troubles with TS.