babel-plugin-transform-vue-jsx

Babel plugin for Vue 2.0 JSX

Requirements

• Assumes you are using Babel with a module bundler e.g. Webpack, because the spread merge helper is imported as a module to avoid duplication.

• This is mutually exclusive with babel-plugin-transform-react-jsx.

Usage

1npm install\
2  babel-plugin-syntax-jsx\
3  babel-plugin-transform-vue-jsx\
4  babel-helper-vue-jsx-merge-props\
5  babel-preset-env\
6  --save-dev

In your .babelrc:

1{
2  "presets": ["env"],
3  "plugins": ["transform-vue-jsx"]
4}

The plugin transpiles the following JSX:

1<div id="foo">{this.text}</div>

To the following JavaScript:

1h('div', {
2  attrs: {
3    id: 'foo'
4  }
5}, [this.text])

Note the h function, which is a shorthand for a Vue instance's $createElement method, must be in the scope where the JSX is. Since this method is passed to component render functions as the first argument, in most cases you'd do this:

1Vue.component('jsx-example', {
2  render (h) { // <-- h must be in scope
3    return <div id="foo">bar</div>
4  }
5})

h auto-injection

Starting with version 3.4.0 we automatically inject const h = this.$createElement in any method and getter (not functions or arrow functions) declared in ES2015 syntax that has JSX so you can drop the (h) parameter.

1
2Vue.component('jsx-example', {
3  render () { // h will be injected
4    return <div id="foo">bar</div>
5  },
6  myMethod: function () { // h will not be injected
7    return <div id="foo">bar</div>
8  },
9  someOtherMethod: () => { // h will not be injected
10    return <div id="foo">bar</div>
11  }
12})
13
14@Component
15class App extends Vue {
16  get computed () { // h will be injected
17    return <div id="foo">bar</div>
18  }
19}

Difference from React JSX

First, Vue 2.0's vnode format is different from React's. The second argument to the createElement call is a "data object" that accepts nested objects. Each nested object will be then processed by corresponding modules:

1render (h) {
2  return h('div', {
3    // Component props
4    props: {
5      msg: 'hi'
6    },
7    // normal HTML attributes
8    attrs: {
9      id: 'foo'
10    },
11    // DOM props
12    domProps: {
13      innerHTML: 'bar'
14    },
15    // Event handlers are nested under "on", though
16    // modifiers such as in v-on:keyup.enter are not
17    // supported. You'll have to manually check the
18    // keyCode in the handler instead.
19    on: {
20      click: this.clickHandler
21    },
22    // For components only. Allows you to listen to
23    // native events, rather than events emitted from
24    // the component using vm.$emit.
25    nativeOn: {
26      click: this.nativeClickHandler
27    },
28    // class is a special module, same API as `v-bind:class`
29    class: {
30      foo: true,
31      bar: false
32    },
33    // style is also same as `v-bind:style`
34    style: {
35      color: 'red',
36      fontSize: '14px'
37    },
38    // other special top-level properties
39    key: 'key',
40    ref: 'ref',
41    // assign the `ref` is used on elements/components with v-for
42    refInFor: true,
43    slot: 'slot'
44  })
45}

The equivalent of the above in Vue 2.0 JSX is:

1render (h) {
2  return (
3    <div
4      // normal attributes or component props.
5      id="foo"
6      // DOM properties are prefixed with `domProps`
7      domPropsInnerHTML="bar"
8      // event listeners are prefixed with `on` or `nativeOn`
9      onClick={this.clickHandler}
10      nativeOnClick={this.nativeClickHandler}
11      // other special top-level properties
12      class={{ foo: true, bar: false }}
13      style={{ color: 'red', fontSize: '14px' }}
14      key="key"
15      ref="ref"
16      // assign the `ref` is used on elements/components with v-for
17      refInFor
18      slot="slot">
19    </div>
20  )
21}

Component Tip

If a custom element starts with lowercase, it will be treated as a string id and used to lookup a registered component. If it starts with uppercase, it will be treated as an identifier, which allows you to do:

1import Todo from './Todo.js'
2
3export default {
4  render (h) {
5    return <Todo/> // no need to register Todo via components option
6  }
7}

JSX Spread

JSX spread is supported, and this plugin will intelligently merge nested data properties. For example:

1const data = {
2  class: ['b', 'c']
3}
4const vnode = <div class="a" {...data}/>

The merged data will be:

1{ class: ['a', 'b', 'c'] }

Vue directives

Note that almost all built-in Vue directives are not supported when using JSX, the sole exception being v-show, which can be used with the v-show={value} syntax. In most cases there are obvious programmatic equivalents, for example v-if is just a ternary expression, and v-for is just an array.map() expression, etc.

For custom directives, you can use the v-name={value} syntax. However, note that directive arguments and modifiers are not supported using this syntax. There are two workarounds:

1. Pass everything as an object via value, e.g. v-name={{ value, modifier: true }}

2. Use the raw vnode directive data format:

1const directives = [
2  { name: 'my-dir', value: 123, modifiers: { abc: true } }
3]
4
5return <div {...{ directives }}/>