We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3.2.6
github.com
Reproduction is a copy of https://github.com/vitejs/vite/tree/main/packages/playground/ssr-vue with additon of errorHandler to main.js, and button to Home.vue.
npm run dev Then click the Throw error button on home page.
npm run dev
The custom errorHandler gets called. Which logs 'no error here'
The error is logged to console.
Trying to set up Sentry.
Related to #1336
In callWithErrorHandling, instance is null.
callWithErrorHandling
instance
Add breakpoint to createInvoker. Look back in the stack to hydrateElement. In hydrateElement, parentComponent is set, but not passed to patchProp
createInvoker
hydrateElement
parentComponent
patchProp
The text was updated successfully, but these errors were encountered:
fix(hydration): ensure hydrated event listeners have bound instance (#…
58b1fa5
…4529) fix #4479
app.mount()
stack
Successfully merging a pull request may close this issue.
Version
3.2.6
Reproduction link
github.com
Steps to reproduce
Reproduction is a copy of https://github.com/vitejs/vite/tree/main/packages/playground/ssr-vue with additon of errorHandler to main.js, and button to Home.vue.
npm run dev
Then click the Throw error button on home page.What is expected?
The custom errorHandler gets called. Which logs 'no error here'
What is actually happening?
The error is logged to console.
Trying to set up Sentry.
Related to #1336
In
callWithErrorHandling
,instance
is null.Add breakpoint to
createInvoker
. Look back in the stack tohydrateElement
. InhydrateElement
,parentComponent
is set, but not passed topatchProp
The text was updated successfully, but these errors were encountered: