Version

3.0.7

Reproduction link

https://jsfiddle.net/eaj9y68p/

Steps to reproduce

Current version of Vue@next throwing error in console and asks to log this to Vue team, so I'm here.

So I'm using variable in root component that got renamed, and child component still have old variable name, and that's basically what causes this error in a console.

Example: https://jsfiddle.net/eaj9y68p/

What is expected?

Some meaningful error message pointing to template line where variable is not resolved.

What is actually happening?

There is no error message except of Vue's warning about Unhandled error during execution of scheduler flush..

Console output:

[Vue warn]: Property "errorTypes" was accessed during render but is not defined on instance. at warn @ vue.global.js:1254

[Vue warn]: Unhandled error during execution of render function at warn @ vue.global.js:1254

[Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please open an issue at https://new-issue.vuejs.org/?repo=vuejs/vue-next at warn @ vue.global.js:1254

..

Uncaught (in promise) TypeError: Cannot read property 'BROWSER' of undefined at Proxy.render (eval at compileToFunction (vue.global.js:13613), :73:42) at renderComponentRoot (vue.global.js:1943) at componentEffect (vue.global.js:5464) at reactiveEffect (vue.global.js:410) at callWithErrorHandling (vue.global.js:1370) at flushJobs (vue.global.js:1596)

You have a typo: errorTypes0

Please, next time consider using the forum, the Discord server or StackOverflow for questions first. But feel free to come back and open an issue if it turns out to be a bug 🙂

@posva I know, shouldn't there be render error if a typo occurs? That was basically issue report meaning.

@posva I thought Vue shows line number of error or something (in full dev mode) maybe I was wrong, sorry