-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Description
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.2.0
Framework Version
2.6.14
Link to Sentry event
https://sentry.io/organizations/withthegrid/issues/3357123868/?project=242657&query=is%3Aunresolved
Steps to Reproduce
Very similar to #5204, I don't know exactly how, but with attachProps enabled the errorHandler looks for propsData in vm.$options, which is undefined in this case.
sentry-javascript/packages/vue/src/errorhandler.ts
Lines 20 to 24 in d4c153b
| if (vm && options.attachProps) { | |
| // Vue2 - $options.propsData | |
| // Vue3 - $props | |
| metadata.propsData = vm.$options.propsData || vm.$props; | |
| } |
Expected Result
To not have sentry erroring
Actual Result
I get an uncaught error thrown by the SDK landing in my Sentry dashboard
I should have changed the types here in my previous fix #5254 :
| $options: { |
This way I would have seen a TS error in the errorHandler
Metadata
Metadata
Assignees
Labels
No labels