Vue Babel Preset Jsx

Posted on  by admin

From all the available JavaScript frameworks, I’d say that Vue and React are my favorites. React for its vast ecosystem, great TypeScript support, JSX, and Vue for its simplicity, performance, and some smaller life quality improvements, like auto-passing props, easy-to-use transitions system, directives, slots & more.

Current Tags

So, how about getting the best of both worlds? Get Vue’s benefits in React would mean making React into Vue, so that’s not an option.

  • How to use TypeScript and JSX in Vue then? Well, Vue is heavily reliant on its custom templating syntax and SFCs (Single File Components).
  • However, it’s also very “unopinionated” and provides its users with many ways of doing the same thing.
  • This includes using JSX, even TSX (JSX with TypeScript)! Sadly, when you do many things well, you usually can’t do a single thing great.

Installing in an Already Created Project #


Let me demonstrate that through Vue 2’s TSX support. Let’s start with pure JSX. A quick search on Vue 2 docs brings the following results:. There’s certainly not a lot of it, but potentially that’s all we need?

The link redirects us to a GitHub README, detailing the installation of the required Babel plugin and the general usage of JSX with other Vue features.

Stay tuned!

Add required dependencies first (I’m using Yarn here):.

Configure Babel:. Now, if you’re lucky, you should be able to just jump into your code and write JSX.

  • If you’re not, you’ll encounter a few errors on the way.
  • Most of them should be easy to fix by browsing the Babel plugin’s GitHub issues or searching elsewhere on the web.
  • However, resources on this subject are quite limited relative to Vue’s popularity.

When you eventually get to writing your Vue JSX code, things should be pretty good from here. Your JSX should be compatible with SFCs, and you shouldn’t even have to use the components field for them to work!

With JSX in place, we can proceed to replace the “J” with “T” by bringing TypeScript into play! Using the same method as before, we’ll first set up TypeScript alone.


Now, Vue 2 docs have a whole page dedicated solely to TypeScript support, so I won’t complain there.

It details the configuration process, caveats, and different ways in which you can use TS with Vue (“unopinionation” - remember?).

There are 2 main ways to use TS with Vue - the basic one and the “class-based” one. For the “class-based” approach, I must admit that I’m not really into it. Maybe it’s because I’m more into the “functional-style” programming lately, or maybe because I don’t like ES decorators.

For me, they’re too experimental right now, and - in TypeScript - they don’t provide the same auto-completion as all the other “well-established” features.

Anyway, there’s a whole site dedicated to the “class-based” Vue components and their use with TypeScript, so feel free to check it out if you’re interested.

Setup and configuration

As for the basic approach, you simply wrap your component object inside Vue.extend() , and that’s it. You’ll still need to use to annotate your props, render() method, and all computed properties with PropType, VNode, and your type of choice, respectively.

The snippet above is an adaptation of the previous one for TypeScript. I left the JSX, but there are a few issues with it that I’ll get into.

Who is using

  • But before that, I wanted to mention a “shim” file which you’ll need for TypeScript to not freak out on *.vue file imports:.
  • Put it in in a *.d.ts file in your root folder, within a directory that’s includeed in your TS project, or specify directly in tsconfig.jsontypes property - your choice.
  • However, if you’ve worked with TypeScript declaration files before, you might notice how the above “shim” is flawed.
  • With it, TS will accept *.vue SFCs, but nothing except general Vue properties, will be type-safe.
  • No props, computed, methods, etc. There’s no way around it. You might still get some autocompletion in your code editor / IDE, but that’s only thanks to some patching done on the side - no “pure TypeScript.”.
  • It’d seem like, by combining the JSX and TypeScript setups, we should have TSX ready to go. Sadly, it’s not that simple.
  • You’ll certainly need some more shims to adapt the JSX typings for Vue. Something like the following will do:.


Parallelization #


You’ll also need to adjust your tsconfig.json by setting jsx to ”preserve”.


This will ensure that no TS-related processing will touch the JSX syntax, allowing it to safely reach Babel for proper handling (provided that there aren’t any errors and issues with your setup).



Alright, now you should be good to go! Enjoy your top-notch Vue TSX experience… yeah. Let’s talk about that. The reason I’ve just walked you through the generic Vue 2 TSX setup isn’t really to showcase “how to” do it.

Babel Compatibility Notes

It’s to show you “how flawed” the whole process is. Sure, it might be useful when converting an existing project or boilerplate, but most of the time, you’ll do just fine with Vue CLI and a proper set of plugins or a no-config bundler like Parcel or Poi.

Caching #


However, this won’t fix the plethora of potential setup issues or lack of in-depth documentation. More than that, none of these ways will grant you proper TSX experience, as you might know it from React. Talking about the experience, what it’s like?



Attributes / Props

After spending some time with it, I must admit - it’s not good. In terms of editors, there are only 2 players that count - VS Code and WebStorm. I used Vue with Vetur extension.

Editor support

However, it doesn’t matter, as this extension focuses mostly on SFCs support (it lacks in this area too). There’s also the VueDX extension that works much better than Vetur for SFCs, but it completely breaks the JSX/TSX support, so I had to disable it.

TSX combo


In TypeScript

Now, both editors were close, with WebStorm coming slightly ahead. Props autocompletion was mostly non-existent, and while working within components, all.

13 Versions

this-related interactions were hit or miss, however generally better on WebStorm. Now, where there’s a problem, there’s also a solution.

And for Vue 2 TSX support, it’s a “support library” named vue-tsx-support.

It’s a (mostly) TS-only library of types, casting function, utilities, etc., meant to properly type your Vue components and make them work nicely with TSX.

I won’t be going too much into detail here (the GitHub README is pretty in-depth), I would like to show you a usage example of this library:. You can see how the ofType() and convert() casting functions are used to get type-safe Vue components with all the autocompletion goodness.

And with that, I’d say the vue-tsx-support library is the best way to use Vue 2 with TSX right now, and probably forever.

Sure, it is a bit verbose, but it’s the only way to get the proper TSX experience in such a setup. Now, forget all you’ve read until this point, as it doesn’t matter. Alright, maybe I’m joking, but with Vue 3 being in “stable beta” right now, the Vue-TSX combo is set to become much more prominent in the Vue space.


Honestly, that’s what’s the title is all about. I’ve been using Vue 3 extensively for a while now while developing my product - CodeWrite (blogging tool for developers).

And yes, I did use it with TSX, and the development experience was just perfect!

Should you transition?

Vue 3 is now written in TypeScript, giving its support a major boost, and with the new Composition API, it seems like the issue of this has finally been resolved. Sure, the TS and JSX docs haven’t changed much in terms of their clarity, but the setup process as a whole seems to be much less cumbersome.

Configuration #

Debugging Vue.js applications can be difficult, especially when there are dozens, if not hundreds of mutations during a user session. If you’re interested in monitoring and tracking Vue mutations for all of your users in production, try LogRocket.

LogRocket is like a DVR for web and mobile apps, recording literally everything that happens in your Vue apps including network requests, JavaScript errors, performance problems, and much more. Instead of guessing why problems happen, you can aggregate and report on what state your application was in when an issue occurred.

The LogRocket Vuex plugin logs Vuex mutations to the LogRocket console, giving you context around what led to an error, and what state the application was in when an issue occurred.

Modernize how you debug your Vue apps - Start monitoring for free.