Changing VueJS version 2.4.2->2.5.3 breaks the example app
See original GitHub issueHi.
There is a breaking change in VueJS between 2.4.2 and 2.5.3 versions, which makes one of tutorial examples broken.
The docs page that has this example is here https://vuejs.org/v2/guide/single-file-components.html
The tutorial example is here: https://codesandbox.io/s/o29j95wx9
If you update VueJS to 2.5.3 version, then when you try to input a value in a textbox it gets replaced with [object InputEvent]
and you get
[Vue warn]: Invalid prop: type check failed for prop "value". Expected String, got InputEvent. found in ---> <BaseInputText> at /components/BaseInputText.vue <TodoList> at /components/TodoList.vue <App> at /App.vue <Root>
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Breaking Changes - Vue 3 Migration Guide
This page lists all Vue 3 breaking changes from Vue 2. While it looks like a lot has changed, a lot of what...
Read more >How to Migrate from Vue v.2 to Vue v.3 with a Simple Example ...
The new Vue.js version does come with quite a few breaking changes and new features. Also, popular libraries like Vue Router have been...
Read more >Vue.js: How to Migrate a large project from Vue 2 to Vue 3
This new version comes with many new features, optimizations, but also comes with a few breaking changes. Discover our migration story!
Read more >How do I fix a "Vue packages version mismatch" error on ...
This worked for me: Modify package.json : “vue”: “^2.0.8", “vue-template-compiler”: “^2.1.8". Delete node_modules. Run npm install.
Read more >Vue 3 - What's New? What Changed? - YouTube
Vue.js 3 is out! VueJS 2 already was an amazing framework, Vue 3 now improves it even more. It's mostly backwards compatible but...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The example code has now been updated to a new pattern we came up with in the above issue. @tehnetaholic Thanks for bringing this to our attention. 🙂
I think this is actually a bug. It seems that the less specific
v-on=
is now taking priority overv-on:input=
.