0👍
As per Official Vue Docs.
During development, Vue provides a lot of warnings to help you with common errors and pitfalls. However, these warning strings become useless in production and bloat your app’s payload size. In addition, some of these warning checks have small runtime costs that can be avoided in production mode.
In short, Vue doesn’t throw the errors in Production as it is truncated in production build for Vue.
You need to resolve those errors while development in order to work everything properly.
Hope this help!
0👍
In case anybody is stuck on this and Googling around looking for ideas, I had this happen to me as well; I was using a newer JS feature (optional chaining) that worked fine in dev, but then in the production build it broke part of the app. I edited the code to remove optional chaining, and then it worked again.
- [Vuejs]-Vue js, axios: 403 wrong access token even though its the right one
- [Vuejs]-How to use vue.js beforeMount lifecycle mehtod?