volar VS babel-plugin-jsx

Thanks man! Had the same issue and the plugin is indeed causing it. They just released an update (1.0.1) with a fix: https://github.com/johnsoncodehk/volar/blob/master/CHANGELOG.md

🦾 Full TypeScript Support and intellisense for Vuetify 2 components, powered by Volar

Worth mentioning, Volar, the Vue extension for VSCode, implements type checking as JSX just like Svelte.

Hi, I used this config from Volar's GitHub, but whenever I try to do `so %` it gives me an arror

FYI it’s kind of broken at the moment, i had to downgrade. GitHub Issue

With the release of the official version of Vue3, the Vue team officially recommends the Volar extension to replace the Vetur extension, which not only supports Vue3 language highlighting, syntax detection, Also supports TypeScript and type checking based on vue-tsc.

It's also possible to use JSX, as OP's example, using https://github.com/vuejs/babel-plugin-jsx

Even though templates (or let’s say, SFC) is the dominant way to author Vue components, decent JSX support is also provided for both Vue 2 and Vue 3.

I agree - I think JSX does what templating languages have been trying to do for years.

That being said, solid is hardly the only one out there competing that can use JSX:

- https://github.com/vuejs/babel-plugin-jsx

- https://mithril.js.org/jsx.html

- https://preactjs.com/guide/v10/getting-started#setting-up-js...

Apologies, my link above was the incorrect bookmark... that was for Vue 2. Here is the correct link for vue3: https://github.com/vuejs/jsx-next

In a nutshell, you once again have to add jsx: “preserve” to your tsconfig.json and do some changes in your Babel config (it’s a plugin this time):

This exists and works fine - I am using TSX and getting type checking around props etc etc, all the things you'd expect.