[Vue 0.11] Uncaught TypeError: Cannot read property '__vue__' of null

[thelinuxlich]

Getting this error with computed dependencies adding and removing rows of a table(I've incremented the grid example with search and pagination)

Debugger points to this method:

function findNextVm (vm, ref) {
  var el = (vm._blockEnd || vm.$el).nextSibling
  while (!el.__vue__ && el !== ref) {
    el = el.nextSibling
  }
  return el.__vue__
}

[yyx990803]

This is weird because theoretically all v-repeat nodes should always have a nextSibling (with the comment ref node at the end). Need some more details on your setup.

[thelinuxlich]

Closing because I couldn't reproduce it again

[Billiam]

I was able to reproduce this when working with a sorting library ( https://github.com/RubaXa/Sortable ). It looks like, after sorting the last item in a list, the v-repeat comment node was moved from the end to the beginning of my v-repeat/ordered list, and that exception occurs.

Will try to put together a reproduction case.

[Billiam]

Here's an example, with reproduction steps: http://jsfiddle.net/billiamthesecond/75091dcd/

It seems like the sorting library is responsible for the comment getting moved about, but could Vue protect against this error anyway?

If not, is there a way that I could define the repeat so that it did not depend on a comment retaining its position within list?

[zero-is-one]

I had the same problem. I couldn't find a easy fix for this inside Vue. I instead just made sure that the comment was always at the end of the list after sorting. So in your sortable options...

      onEnd: function (evt) {
        this.list.splice(evt.newIndex, 0, this.list.splice(evt.oldIndex, 1)[0]);

        var nodes = this.$$.listElement.childNodes
        for (var i = 0; i < nodes.length; i++) {
          if (nodes[i].nodeName == "#comment")
            var comment = nodes[i];
        };

        if (comment) this.$$.listElement.appendChild(comment)
      }.bind(this)

[japboy]

👍

[CremboC]

Dunno if this is going to help anyone, but in my case I had a track-by="id" and the elements in the array didn't have an id field in them.