What's New In Vue 3.5?

[@DaveStewartLondon]

Props destructuring and defaults looks 🔥

[@LordFullStack]

Haven't touched vue after i got myself into corporate jungle.

[@amitk.512]

Same here. Was using vue since 3 years, got into corporate and have to use react. I miss vue so much.

[@arjix8738]

@@amitk.512 at least you are using react, at my company they are all using angular 16

[@bishowpandey453]

We actually only use Vue at my current job.

[@StyzeSoulmaker]

I've only ever used Vue for work

[@pixiedev]

wow thats amazing, you're using vue in your company. And here I'm react and nextjs 😢 ​@@bishowpandey453

[@ujangaripin7630]

finally 🤤

[@youloulou6591]

Sounds like things that were easy with jQuery will finally rebecome easy today!

[@AnoesjSadraee]

Teleport was already stable, what is new is the "defer" prop.

[@youloulou6591]

@@AnoesjSadraee As the video says "the target had to be already in the DOM". Now you can teleport to a target before it's rendered and it will teleport when the target mounts. This looks a little like the $("some selector").on("click") of jQuery that would happened on elements attached to the DOM after the listener is defined

[@AnoesjSadraee]

@@youloulou6591 that's actually not true, Teleport contents are not automagically inserted "as soon as the target mounts". The rendering of the Teleport contents are delayed one tick. See Teleport docs: "Note that the target element must be rendered in the same mount / update tick with the Teleport - i.e. if the is only mounted a second later, the Teleport will still report an error. The defer works similarly to the mounted lifecycle hook."

[@youloulou6591]

@@AnoesjSadraee Mmmm, thanks for rectifying

[@RazahLP]

Never heard about "Teleport" since now. Thank you!

[@victor141516]

My God... looking at these improvements, for me it's incredible that React is still the leader... Great video! I hope your work keeps the community alive!

[@_Yaroslav]

React is just a legacy monster as Java... It will live long like Kobol or fortran ;)

[@ttaysson]

Its nice to see Vue getting more vuetiful.

[@slava_trushkin]

Finally useId built in. This means icons that need unique ids (used in masks, symbols, filters, some animations) don't have to use weird shenanigans to get unique ids for everything. Waited for this for so long!

[@LearnVue]

that’s a fire use case. what were you doing before

[@slava_trushkin]

@@LearnVue Before there were several solutions: 1. Render icon only after it is mounted, generating random ids. Might sound counter-productive, but it solved hydration mismatch because component renders empty element when hydration happens and on server. Delay between original render and re-render is very small. 2. Rendering icons as background/mask images. One of better solutions, but has issues with animated icons - animation timer starts only first time icon is rendered and cannot be restarted. 3. Using web component. Then icon is in Shadow DOM, no hydration and unique id issues. However, that brings another issue: web components are not always rendered instantly, sometimes there is a delay.

[@luisfrocha1]

Deferred Teleport is a feature I didn't know I needed lol

[@asrorbekmannonov6838]

I think most of the vue devs are waiting for Vapor mode. But 3.5 has is also exciting. 🔥

[@LucasAndrin-i1o]

What are your vscode settings? Such theme and font family.

[@maxwebstudio]

Finaly destructuring props 😃

[@youloulou6591]

Ow yeah!

[@ralacerda12]

With defer teleport, can I keep teleporting a component between routes? Would be cool to do that.

[@ThomazMartinez]

there is issues with defining props in some cases like you do, the colors of tokens is way off. it basically becomes same colors for key and values and the rest, its just weird

[@justafreak15able]

Vue has the best DX of all the frameworks and better performance than many, but people still sleeping on Vue.

[@sadikindikdik]

I’m trying to install Vue 3.5, but every time I run the installation, it only installs Vue 3.4.29. Do you know why this is happening and how I can get Vue 3.5? Any advice would be greatly appreciated!

[@JohnKomarnicki]

Vue 📈

[@jaysonpamittan7530]

Vue still my favorite frontend framework ❤❤❤

[@0-Will-0]

Love Vue!

[@Neeecu]

What font do you use?

[@alunelu111]

I think he's using Dank Mono based on ligatures and styles, which is a paid font.

[@Neeecu]

@@alunelu111 thank you!

[@SolmanNurov]

Thanks

[@shadkamel362]

great update.

[@виртуоз_ру]

Благодарю 👍

[@JeanPereira-g3q]

Cool

[@JEsterCW]

I'm not a fan of destructuring props tho. I love the semantics behind the "props" prefix.

[@ojvribeiro]

I also like to know that a prop is a prop just by looking at it.

[@justafreak15able]

You still can use both. Just mention it in your company's styleguide.

[@leonsnajdr9767]

fancy

[@photostu]

Teleport defer should really just be the default, I think we can all wait a cycle to move something, eh?

[@AnoesjSadraee]

Why? Most times I use Teleport, the target is outside of the Vue root element. Think of things like a tooltip wrapper. Why would you defer that? It would add a bit of delay, most likely around 16.7ms (60 fps), but that's just an assumption I'm making here.

[@FaithTran-m2f]

Kunze Glens

[@Icaruj]

Nuxt is trash, ask any dev trying to migrate a non trivial production app from Nuxt 2 to Nuxt 3, no thanks. I would rather use pure Vue than that 💩

[@bitmazing6465]

Just my two cents: There is Nuxt Bridge for that, which allows you to incrementally upgrade the app from Nuxt 2 to Nuxt 3. Every major version brings breaking changes, it's part of the life cycle of frameworks and tools. Saying it's trash just because it has breaking changes like every other framework in existence is a bit irrational here. Not to mention there was plenty of breaking changes between Vue 2 and 3, Vuex and Pinia, etc etc. On the bright side, migration from Nuxt 3 to Nuxt 4 is expected to have little to no breaking changes, and the process would be much smoother than Nuxt 2 -> 3.

[@delir0]

who cares about vue in 2024?

[@LostInAutism]

You it seems. Clicked the video that's titled "What's New In Vue 3.5?" by LearnVue. Don't know what you expected. Go back to your vim dungeon heathen while true frameworks eat your lunch.

[@arkeynserhayn8370]

​@@LostInAutism Unnecessary shade at vim, but OK