-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Production handles warnings differently from development #5867
Comments
This is the way all Vue warnings have always worked:
|
For this specific case the error behavior is indeed inconsistent. It should also error in dev. |
|
…alid v-for range close vuejs#5867
Version
3.2.33
Reproduction link
sfc.vuejs.org/
Steps to reproduce
have a template with a list greater than 1, with length spelled incorrectly, that looks like:
What is expected?
Consistent warning/error handling between environments
What is actually happening?
Development shows no template error, test shows a warning, production hard errors.
Even the playground shows a warning on load, but still renders, would be nice for prod and development to do the same.
We recently had a bug that prevented the page from loading in production.
Obvious failure since length was spelled wrong. What was weird though was that no error or warning showed up in development and the page loads fine. In test, I get
but the page still loads fine. And in production, a hard error, page doesn't load.
Some consistency would be nice, or at least a way to change the behaviour.
The text was updated successfully, but these errors were encountered: