Ask us about:
- Using Vue.js
- Contributing to code base
- Vue.js roadblock
- General Programming advice
Message from the host 💬
Thank you for joining our AMA. The questions were brilliant; we all had much fun answering them. Here is a summary of the AMA:
- Vue 2.5 is coming
- vue-cli 3.0 has started and we want the community to participate
- We plan public roadmap to make it easier to get on board and contribute.
- Egoist and Linusborg might or might not be machines/AI
- React patent issues don't affect Vue; we are unlikely to see any issues surrounding this. Vue will remain on MIT license.
- Company backing is not an issue for us. We believe Vue has already surpassed the critical mass and "survival" is really no longer an issue.
- Weex, NativeScript + Vue, and other tooling will be supported by the team for the long term. We are helping to mature the documentation and bridge the gap to help adoption.
- React Fiber is interesting. Vue can leverage some learnings, and we will watch the space. Although we don't see a strong need to implement something similar.
- Vue 3.0 is in the planning phase, targeting evergreen browsers. This will help us enhance the reactivity system and reduce library size. 2.x and 3.x will be maintained in parallel.
- Web components will not (yet) be part of core, but we will continue to watch this space
- We wish Wordpress all the best with their upcoming challenges and will support them as much as we can. It's still too early to say what will happen here, but we are very excited as a team on the prospects it brings.
Are there any plans for an official package, similar to React Native, for Vue?
Do you feel that if Vue has a Native package (Vue Native 😎), it's adoption would see a rapid growth and hopefully be adopted & supported by major players?
Thank you for your amazing work. Kudos 🙌
I love Vue for its great simplicity to use, the high quality documentation, and the entire ecosystem* around it. What are the next major efforts for the team and how or where can I best follow those efforts?
(aka if I see something I can help with, I'd love to, otherwise just follow)
*vue-cli, easily used and extended templates, VS Code's vetur, Chrome DevTools extension
Vue.js is definitely mature. I see new upcoming challenges as heading toward definitive growth and more "React-ish" kind of moves tempting you.
What do you think it would take to stay true to your initial mission and values despite external forces pulling you in different directions?
Because I know you want to keep your independent style and approach. And that's awesome.
Hi Vue.js team ! I falled in love with vue-class-component and vue-property-decorator, and all my Vue projects are now using them. Now that class and property decorators are stage 2 at tc39, I was wondering if you plan to make an official template which use decorators (either ES6+Babel or Typescript).
What did you plan about mobile app ? I follow weex but documentation is a little obscure and i don't see lots of project using it in production (some chinese company but it's all). Did you think weex and his documentation are production ready ?
Else we have other alternatives with nativescript and vue (but still in progress), OnsenUI for not native apps ...
What is the best way for mobile apps with vuejs ?
Using the opportunity, can you guys officially and honestly confirm or deny that Egoist is an artificial intelligence written by Evan to solve all Vue-related problems, one package a day? I know many people who are raising such suspicions, because of how active he is in the ecosystem and how high quality his packages are.
I try to follow Vue community close but so far I have yet to find a popular Vue package written by a woman. It's of course highly possible they are parts of larger teams or stay behind package names, but except for Sarah Drasner who makes high quality tutorials, courses and talks about Vue (and codes brilliant animations), we don't see women active in Vue community. What can we as fellow developers do to make the community more open for them?
Not sure if these questions are best for here or another forum.
Question 1: Vue developer tools works amazing when working on small scale applications with simple mution paths, but anytime we try to use it in our complex mutation webapp it crashes instantly with the increase in mutations. Is there a plan to improve the performance of the dev tools?
Question 2: Vuex Plugin examples for sockets isnt extremely clear, especially if you are subscribing to multiple sockets and I have not been able to find an example of anyone else using plugins extensively. How would one best integrate with Sockets for vuex?
My company has a big code-base (mainly a component library) written in Angular which we'd love to port to Vue but it's too much work to do it in one go.
Are there any plans for an official way to use Vue in existing AngularJS apps to slowly transition? There are a few tutorials and 'hacky' suggestions on the web but I think lots of people would make the jump if it was easier.
I'm just a-week-old-Vue-developer ;) I mainly code using ember.js! I feel vuejs as a combination of various frameworks (react - say, flux architecture, angular - say, HTML attribute kind of things and ember - say, computed properties ). Is that true that Vue was born by integrating all the pros of various frameworks?
I have really loved learning Vue this year, I am new to it. I come from a backend development background so don't have a lot of the front-end expertise as a lot of other folk. A challenge I have found is making decisions in design and frameworks that have big impact on your project. Once you are committed there is a lot of effort to change For example I am using Vue with Nuxt and Vuetify. I want to see how SSR behaves and I want a GUI framework that is responsive and supports this design choice. But that is just one of many options.
What is the most common / recommended setup for Vue projects?
One of my concerns is for these other frameworks as well. I don't think Vue is going anywhere but who says Vuetify is going to be around in a year or maybe something new would be the next big thing.
Any suggestions on what we can do to best decide on what core components / frameworks to use?
thanks for all the great work you guys do by the way.
Hey, Why Vue doesn't use custom tags (like some other frameworks) and and prefers changing it into div or any other valid tag ? (actually I'm fan of this method) And my other q : Since I'm Ember dev too, Is there any plan to create anything like EmberData in Vue too? cause that's awesome and really helps in big projects.
Vue is awesome, and our project is considering using it. However, the recently Facebook React Patent issue has raised our attention, does Vue use any patent that holds by Facebook? Here is an extend read about the BSD+Patent license, where the author stats using Vue and Preact may be riskier than using React: https://firstname.lastname@example.org/react-facebook-and-the-revokable-patent-license-why-its-a-paper-25c40c50b562
I'm checking again on using Vue in production for a client. The upstream Vue version deliberately fails mounting on the body element (el === document.body || el === document.documentElement && fail or something like that).
Yes, Vue 2.0 does replace the element it is mounted on, but there is nothing DOM uncompliant in replacing the body, even while this will often fail due to browsers trying to close runaway tags, or 3rd party code doing the same.
I insist on re-enabling mounting on the body element as a very useful thing. When trying to do SEO friendly SSR on our previous projects with vue 1.x, we were very pleased how well it worked with routing. On client-side, routed body element worked like magic to automate things like event listener attachment, setting ARIA attributes according to page content, lang or text direction properties, or changing contextmenu attribute when it was still a thing.
I tried to remove the check and use vue 2 on our past projects, and so far, nothing breaks. The few 3rd party scripts that rewrite the body as a string have to be removed and rewritten for use with an SPA anyways.
Over the last 6 months or so, I've been creating proof-of-concepts for migrating some of my company's large projects to Vue. In doing that, I've come up with some assets/enhancements that are useful for large projects I'd love to feed back upstream (in particular, enhancements to the webpack vue-cli template for building with more configurability, and also a Cordova/Vue template). Assuming you might be interested, what would be the best way to get that in front of you guys and start the conversation?
Hi all, fantastic work you have done with Vue.js so far. I would like to know when the vue-test-utils package will be released. As it would be a definitive must-have for a wider adoption in the company I work for (Orange not to name it). We have a test driven development philosophy for many services and it would help us a lot ! Keep Vue.js as cool as it already is !
A follow up on my previous question that Phan answered,
Phan, do you think I am not aware of the issue with too much code always competing for the document.body? Dan Abramov gives amateurish reasoning on the issue in the article you linked. Do not read his stuff.
A lot of shoddy written third party code competes for document.body or the body sting content, and you always have to rewrite code that runs into conflict while doing so invariably of how you use Vue on the page.
In our case we need to do that. We have complete control over 3rd party code, and we rewrite stuff that misbehaves.
How to get in touch with you guys outside of AMA?