-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
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
warnHandler not invoked prior to app.mount()
due to null stack
/ instance
reference
#5297
Comments
The warnHandler is meant to handle warnings from things happening in components, i.e. during render. it's not meant to catch this kind of warning, really. That's why it receives a vm as the second argument. |
That makes sense, but I'd think that internal Would it be possible for |
This also happens when rendering a component server-side using |
@LinusBorg The default warn handler does not follow that pattern tho, it allows for instance vue-router to create copious amounts of warnings outside of the mount cycle without any way to ignore them. |
Version
3.2.27
Reproduction link
jsfiddle.net
Steps to reproduce
What is expected?
warnHandler
be invoked for all warnings, even if app is not yet instanced / mounted.What is actually happening?
warnHandler
is skipped and internal warn handler runs.Potentially related:
#4479
The text was updated successfully, but these errors were encountered: