Remove Vue.util.formatComponentName usage as it's not present on production

[diogobeda]

As you can see on the code below, Vue.util.formatComponent is not present on production bundles, so raven shouldn't depend on it for getting component names:

https://github.com/vuejs/vue/blob/51e7608528c2e958e3705425bad3d6325ce97765/src/core/util/debug.js#L7

That causes sentry to not capture any error at all. It instead throws this error on console:

This function is not subject to many changes, so I think we can just copy its content and update if needed on the future. What do you guys think?

[benvinegar]

I am super hesitant to accept changes that rely on internal properties and methods. We don't know if these will change or not. Maybe with the blessing of @yyx990803.

I'd sooner say: let's attempt to use formatComponent if it's available, otherwise it becomes "anonymous component".

[yyx990803]

All of these three internal properties (_isVue, $options._componentTag and $options.__file) are unlikely to ever change. Their usage also won't throw any errors even if they do change - the worst case scenario is returning anoymous component. So I'd say it's safe to use this method here.

[nddery]

Any chance of seeing a patch release with this fix ? We've been wondering why Sentry had been so silent..

[rtheunissen]

@benvinegar also waiting for this to be released, we have multiple cases on production that aren't reaching Sentry because of this issue.

[benvinegar]

@nddery @rtheunissen – it's out now in 3.11.0. Sorry for the delay; I try to make sure I only publish new versions when I am available to triage any potential new issues that pop up as a result of the release.