Evan You's State of the Vuenion 📣 VueConf US 2023

The creator of Vue.js updates the community on the roadmap for the Vue.js framework for 2023 at VueConf US in New Orleans.
Ready to master Vue.js? With weekly Vue js tutorials on the latest topics, and exclusive content with Evan You (the creator of Vue), Vue Mastery is the ultimate learning resource for Vue developers to level-up their skills. Watch more free Vuejs tutorials 👉 www.vuemastery.com/courses
0:00 Intro
0:58 Vue 3.3 is released
2:09 Focus: script setup + Typescript DX
4:02 Imported & Complex Types support in SFC Macros
4:56 Generic Components
6:24 More Ergonomic defineEmits
8:08 Typed Slots with defineSlots
9:25 Reactive Props Destructure
12:02 defineModel
13:19 defineOptions
13:47 Getter support via toRef & toValue
17:36 JSX Import Source
18:52 What's next?
18:59 VitePress 1.0
20:09 Vue core issue / PR cleanup
20:22 Plans for upcoming 3.x minors
22:08 Vapor Mode
23:26 Vapor Mode stages
27:58 Future Standards to Track
33:56 Thank you

[@kosyauzer4787]

That defineModel macro is such a good upgrade. Much love to the team

[@hscsoft_tutorials]

Love vue. easy easy easy, fun fun fun,

[@Norfeldt]

Been doing Vue 3.3 for over a month now and I must say it's a great experience. Interesting road map for 2023. One thing that I was hoping to see is some focus on routing - I would love to (more easily) move state into the URL instead of a store like pinia. It make page refresh stable and allows building E2E test jump right into a state/context.

[@tobychidi]

In the Vue team I trust. 😊. These guys are good.

[@clintonmoshe9544]

I am a react guy but i am thinking of giving vue a try.

[@faridguzman91]

please do, we need more vue developers since now react wants the dev monopoly and with nextjs its not going the right direction

[@dominuskelvin]

You are gonna love it

[@clintonmoshe9544]

@@faridguzman91 I will, I didn't like this move.

[@yueyu9762]

Same here. Vue seems pretty awesome to me so far.

[@heroe1486]

@@faridguzman91 I've literally switched to Vue (tried solid but the ecosystem isn't there yet) from React after years because of NextJS new (unstable) nonsense and React's" you should use a Framework if you build apps with React" statement. Vue was actually my first JS framework but I preferred React back then after trying it, now with Vue 3 + script setup and composables (hooks equivalent) it feels way smoother than it used to.

[@jean70242]

Been using Vue since 2.1, not really sure, in the early days. And never looked back. With Vue 3.x, the options API is now a thing of the past. Big up to the Vue team. 🎉🎉

[@alwaisy]

I was waiting for this video.

[@jntaca]

Vapor Mode will "vaporize" all those Svelte and Solid conceited guys.

[@faridguzman91]

i love all of this

[@hahiZY]

amazing, I am using all vue, nuxt and vitepress...haha sounds like a bunch of new features are coming. Indeed, the nuxt virtual dom and actual dom mismatch thing is a bit annoying tho XD

[@sebastianwei542]

Where can I find the documentation for 9:25 Reactive Props Destructure?

[@metalsadman]

that generic script setup is great, I'm having a hard time upgrading with 3.3.x tho, I'm having some compilation error that doesn't make sense :s.

[@arnonrdp]

11:00 Guys, I think this would be a good approach: const props = defineProps

[@samuelmorkbednarzkepler]

This is mixing types and JS though which probably breaks some fundemental stuff? It would make more sense to do this: const props = defineProps({ foo: number = 1 }).

[@arnonrdp]

@@samuelmorkbednarzkepler you’re totally correct.

[@cooltune]

Still scratching my head over why JSX is still a thing. Are there any use cases where using it over the regular SFC-template approach has any benefits? I remember specifically and clearly choosing Vue over React because the thought of template logic inside javascript felt hacked together and utterly wrong. Been stuck with Vue-templates (infused with pug notation) ever since.

[@heroe1486]

Some people prefer the versatility of JSX, and you can make JSX less bloated with few components like or like Solid does, even Vue libraries like Vuetify use it. I personally don't mind both, template languages feel cleaner and JSX more powerful and natural since it just feels like JS, but both are ok.

[@disservin]

I agree, though one advantage I've heard someone mention were recursive tree structures. You might say you can do this with normal components just fine but it creates more instances of that component.

[@jwoods9659]

It means React devs can switch over

[@ananthakrishnanbaji7956]

It has been three years since Vue 3 was released. Why is the Suspense feature still considered experimental?

[@dasten123]

to keep us in suspense

[@ikbo]

What is Vue's equiiof react server components (RSC)?

[@wojciechosinski5927]

Nuxt Server Components

[@chenxi5479]

Vue with PHP

[@user-kr7nz5hy9f]

great

[@giokuan2327]

I'm the second one🤩

[@dlef]

.value is easy but it's just not honest

[@mbokil]

I agree. It seems sort of clumsy. I look at Svelte's syntax and it is so clean and simple. It is a shame they abandoned reactivity transform. Luckily it is being maintain by VueMacros now and you can add it as a plugin.

[@hscsoft_tutorials]

I am the first one.

[@bloodjopa]

It's all about composition api. Not interesting

[@samuelmorkbednarzkepler]

composition api is awesome

[@bloodjopa]

@@samuelmorkbednarzkepler it is not

[@samuelmorkbednarzkepler]

@@bloodjopa why? It lets you group related lines of code together. It also lets you easily extract shared logic into hooks which is what allows for vueuse to exist - which is easily the best thing to ever happen to the Vue ecosystem. It also lets you write the same code everywhere, both inside Vue components and I plain JS files which is another massive improvement that puts Vue ahead of all other major frameworks. All in all composition API lets you keep big components organized through better code composition. And it lets you share logic that looks and works the same in all contexts. Not to mention that functional programing is where the entire industry is headed. So what's bad about it? I think it's the biggest win I've ever seen in any framework ever

[@virtuoz-ru]

Благодарю 👍