$options missing in vm when catching exceptions in Vue components

[Arinono]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which package are you using?

@sentry/vue

SDK Version

7.0.0

Framework Version

2.6.14

Link to Sentry event

https://sentry.io/organizations/withthegrid/issues/3317080749/?project=242657&query=is%3Aunresolved

Steps to Reproduce

Honestly, I don't know.

We are using Vue 2 and had no issue with sentry v6 and Integrations.Vue. When we migrated to sentry v7 (with @sentry/vue), reports started to come in our dashboard with this error.

I know of an existing issue with the same behaviour (#1270), but since a lot has changed since then, I figured a new issue made more sense.

Expected Result

To not have Sentry erroring

Actual Result

When formatComponentName is called in the errorHandler vm.$options is undefined, triggering the error.

[AbhiPrasad]

Hey, thanks for writing in! Backlogging this issue for the team, but in the meantime PRs are welcome for anyone who wants to help out.