Vue-devtools: Property or method "_isBuffer" is not defined on the instance but referenced during render.

[ProBun]

Version

5.0.7

Browser and OS info

Chrome 73.0.3683.86

Steps to reproduce

Open vue-devtools on vue app and switch route

What is expected?

No errors in console

What is actually happening?

Throwing error Property or method "_isBuffer" is not defined on the instance but referenced during render.

[ashishov]

I have the same issue, but not on all vuejs projects.

[Landen13]

Same issue

Installed beta version (5.0.0) instead of main one.

[Akryum]

Please provide a runnable minimal reproduction.

[ProBun]

https://github.com/ProBun/vuedevtools-issue

When you switch beetwen to routes it breaks

[Akryum]

@ProBun The repository only contains hello world components.

[ProBun]

Sorry forgot to add them to git repo

[ProBun]

@YESENE Just switch route using one of the links on homepage

[wizbit]

I've had this, but only when 'vuex-router-sync' is setup and changing routes.

[jgmcelwain]

For what it's worth, I do _not_ have vuex-router-sync in my project but am experiencing the same bug.

[mbranicky]

The same problem here, when changing route, on almost all components. Not using vuex-router-sync

[JFonsecaSpot]

@jgmcelwain and @mbranicky can you tell if you have arrays stored on vuex and if those route changes render components using those arrays? My issue seams to be triggered when using array functions (forEach, filter, sort... etc) on computed values.

[jgmcelwain]

@JFonsecaSpot Yes, I have stored arrays and have computed props based on said arrays that use those Array methods.

[mbranicky]

@JFonsecaSpot Yes I do. Arrays in VUEX and components rendered based on these arrays.

[vchapple17]

I also have this issue. I reverted to 5.0.0 in Chrome Extensions.

https://chrome.google.com/webstore/detail/vuejs-devtools/ljjemllljcmogpfapbkkighbhhppjdbg.

I look forward to a fix, or someone explaining what else I can try if its not an issue with vue devtools.

[jgmcelwain]

I look forward to a fix, or someone explaining what else I can try if its not an issue with vue devtools.

@vchapple17 the issue is labelled as fixed in 2ff9785 and should be working when a new release is pushed.

[gapnav]

I also have this issue. I reverted to 5.0.0 in Chrome Extensions.

https://chrome.google.com/webstore/detail/vuejs-devtools/ljjemllljcmogpfapbkkighbhhppjdbg.

I look forward to a fix, or someone explaining what else I can try if its not an issue with vue devtools.

How did you get this link? I see that this link is to chrome webstore (not third-party service), but I can't find way to see old versions.

[vchapple17]

How did you get this link? I see that this link is to chrome webstore (not third-party service), but I can't find way to see old versions.

@gapnav
This particular link is to the beta channel with is for 5.0.0, which for me was far enough back to help with the issue.

There are currently two vuejs-devtools extensions, one for the 5.0.0 and one for the current release 5.0.7 (https://chrome.google.com/webstore/detail/vuejs-devtools/nhdogjmejiglipccpnnnanhbledajbpd)

[ghost]

The solution is uninstall and install extension chrome of Vue

[DespertaWeb]

@carlosgbp00027 is right. There's already an update:

uninstall and reinstall

https://chrome.google.com/webstore/detail/vuejs-devtools/nhdogjmejiglipccpnnnanhbledajbpd/related