Recursive components problem: Vue.component() does not respect "name" prop defined in options

JSFiddle: http://jsfiddle.net/fenivana/wso9prne/

Vue.js version: latest

tree.js:

module.exports = {
    name: 'v-tree',
  props: ['list'],
  template: '<ul>' +
              '<li v-for="item in list">{{item.value}}' + 
                '<v-tree v-if="item.children" :list="item.children"></v-tree>' + 
              '</li>' +
            '</ul>'
};

app.js:

var tree = require('./tree');

// registered the tree component with a different name
// e.g. add namespace
// this will cause error
Vue.component('ns-tree', tree);

// but if I registered it with
// Vue.component('ns-tree', Vue.extend(tree));
// this works fine.

new Vue({
    el: 'body',
    data: {
        list: [
        { value: 'foo' },
        { value: 'bar', children: [
          { value: 'baz' }
        ] }
      ]
    }
});

app.html:

<ns-tree :list="list"><</ns-tree>

Throws error:

VM408 vue.js:1018 [Vue warn]: Unknown custom element: <v-tree> - did you register the component correctly? For recursive components, make sure to provide the "name" option.

Using Vue.component('ns-tree', Vue.extend(tree)) works fine, but this is verbose, and I need to tell the users of this component that you need to call Vue.extend() before Vue.component(), or you must register as the same name as the internal name.

[appurist]

BTW, I found this issue because I was getting the did you register the component correctly? error as well. It seems the name member of a single-file .vue component is ignored. I’ve stopped including the names there, and started naming them in the components: member where they are referenced (or globally as above), e.g.:

import MyComponent from '@/components/MyComponent.vue';
export default {
  components: {
    'my-component': MyComponent
  }

That will only be valid there, but the other approach above can be used for global registrations.

It seems more appropriate to me to only register them where they are used (locally), however I’m not sure of the performance impact of registering them locally repeatedly, if it’s a component nested within many components.

[yyx990803]

I think this is something that can be fixed since the expected behavior is reasonable.