Tutorial site for Vue.js developers covering Vue CLI, Vuex, Nuxt, code splitting with Webpack, and Laravel integration.
HN commenters link it for practical Vue guides, such as tips for large Nuxt apps, Vue CLI 3, and a Vue and Laravel CRUD app.
You're not making it clear why it's unconvincing. Let me summarize my post: Vue had to fundamentally introduce a new concept (which developers, myself included, find confusing [1]) to solve a problem you can easily solve in React without any additional APIs. React does this very much by design [2] and it's a huge part of the reason why I like it more than Vue.
1. https://vuejsdevelopers.com/2017/10/02/vue-js-scoped-slots/
2. https://2014.jsconf.eu/speakers/sebastian-markbage-minimal-api-surface-area-learning-patterns-instead-of-frameworks.html
Web components have been a possible build target for Vue for a while. It seems totally possible to set up a Vue project like you’ve suggested, use all the Vue conventions & tooling, and output web components that you then use a la carte. Maybe I’m missing something about what you are looking for, but more details are here: https://vuejsdevelopers.com/2018/05/21/vue-js-web-component/
And I’m sure the same can be done in other frameworks.
You can use custom routing and its actually recommended for bigger projects you can check it here if you want https://vuejsdevelopers.com/2018/07/16/7-tips-large-nuxt-app-vue/
Here's an article that discusses v3: https://vuejsdevelopers.com/2018/03/26/vue-cli-3/.
https://vuejsdevelopers.com/2018/02/05/vue-laravel-crud/