If only the top developers on TH-cam would promote Vue more... but they all catter to the React demographic... non stop!!! Every time I check my notifications and see a new Fireship video, it's either about A.I. or React, and ocasionally about some other new technology. Videos for views/likes/engagement about all the flaws React has, that Vue already solves, BIG LOL! Thanks for being here for the Vue community!!! 🤝🔥
BTW, the reason they picked Rurouni Kenshin is because that anime is getting a remake that is slated to be released very soon. Just a bit of trivia for you folks from a die hard of the original when I was a kid.
If you are outputting the "num" as HTML, then the return would be a string, right? To test it we would want to invert to expect a number to be returned and see if TypeScript caught that as an issue.
That is true. The way the {{ }} is compiled uses "toDisplayString", which, simply put, converts any value you pass to a string edit: And there is no way to change that output, because the compiler doesn't really know about types or what is expected.
If you do {{typeof num}} it's a number. So it's not a string. If you just add in 5, then it's a string by default. But it inherits the type that you set since it's a variable set in the script setup.
It's cool. Not sure why they want to make Vue like react. I'm confused by that, I picked vue because I didn't like the syntax of react. So seeing it turn into react is concerning. I'm still on Vue2 because migrating 20+ projects isn't simple. But I'm starting to wonder if I should even bother or should I just switch to react?
is there a way to make my components implement an interface? My idea is to force components to implement certain method types, in my context for page analytics
I still don't know how do a simple button wrapper in `Vue`. :( Example... In react, I would just go `const Button = (props: JSX.IntrinsicAttributes['button'] & { myCustomPropTypes }) => ` I don't know how to do the same `JSX.IntrinsicAttributes['button']` in Vue.
This is actually much simpler in vue. Your Button Wrapper component will automatically inherit the attributes of its child button. Have a look at the fallthrough attributes guide in the vue docs. If you want to be more explicit, there is also an interface called ButtonHTMLAttributes which is similar to JSX.IntrinsicAttributes['button']
@@tsolanoff I stuck with version 2 because of broken backward compatibility. Spend a time learning how to migrate to version 3 and now need to spend a time again for learning how to migrate to version 3.3.
@@yatsuk the major part of all web apps are not being constantly updated just because they do their job. Migrating to new technologies requires many efforts and makes sense only if the current state can’t afford adding new features or supporting proper workability anymore. So as long as your app is working as it’s supposed to there is no need of migration. And you could develop your new projects using new version to follow up the tends.
does eslint support destructuring the props? i'm still seeing the error "...Destructuring the `props` will cause the value to lose reactivity.eslintvue/no-setup-props-destructure ..."
![[TH] 2024 PMSL SEA Finals D1 | Fall | ยิงต้องโหด ให้เหมือนโกรธกันมาก่อน](http://i.ytimg.com/vi/OnTdfGySmds/mqdefault.jpg)
I have a discord if you'd like to chat more ! discord.gg/8VE2QK2h Also check out my live streams on Friday on this channel! :)
I am learning react. This looks ugly
discord link is not valid, update it please
Link isn't working
Im actually thinking about trying Vue now. Evan is great.
Awesome!
You should! It’s great!
Vie is great for a ton of projects. Trust me, it’s very enjoyable!
The way people use "it changes everything" in every title changes everything! 😂
Good video, thanks!
learning Vue at the moment and I learn a lot from your content. Thanks Erik
You are welcome!
upgraded already. what an update.
For sure!
That is the support for Typescript that I wanted since the beggining. Really loved this release
Love the shirt! Go Bolts!!! ⚡Can't wait to try out Vue 3.3 proper!
Thanks! I'm a fan.
I wonder if Suspense will ever get out of the experimental state in one of these releases (feels like it’s been years)
Could you please do a detailed videos on these new features so that beginners can understand as well. Thanks
Sure!
love Vue but... seems to be embracing type complexity as opposed to remaining a clean framework.
So many people like myself chose Vue cause it was simple and now it is starting to look like garbage.
yeah, vue + ts = confusing, unlike react + ts = awesome
Wow I am so excited to use these features, Thanks
If only the top developers on TH-cam would promote Vue more... but they all catter to the React demographic... non stop!!!
Every time I check my notifications and see a new Fireship video, it's either about A.I. or React, and ocasionally about some other new technology. Videos for views/likes/engagement about all the flaws React has, that Vue already solves, BIG LOL!
Thanks for being here for the Vue community!!! 🤝🔥
BTW, the reason they picked Rurouni Kenshin is because that anime is getting a remake that is slated to be released very soon. Just a bit of trivia for you folks from a die hard of the original when I was a kid.
If you are outputting the "num" as HTML, then the return would be a string, right? To test it we would want to invert to expect a number to be returned and see if TypeScript caught that as an issue.
That is true. The way the {{ }} is compiled uses "toDisplayString", which, simply put, converts any value you pass to a string
edit: And there is no way to change that output, because the compiler doesn't really know about types or what is expected.
If you do {{typeof num}} it's a number. So it's not a string. If you just add in 5, then it's a string by default. But it inherits the type that you set since it's a variable set in the script setup.
Hold on, I've been using typesafety in Nuxt3 for a while now... You mean it's not always been there? I've been living in the future.
It's cool.
Not sure why they want to make Vue like react. I'm confused by that, I picked vue because I didn't like the syntax of react. So seeing it turn into react is concerning. I'm still on Vue2 because migrating 20+ projects isn't simple. But I'm starting to wonder if I should even bother or should I just switch to react?
If you don't like Vue leaning into React - consider Svelte.
defineProps({selected: {type:Number}}) was doing the same thing
is there a way to make my components implement an interface? My idea is to force components to implement certain method types, in my context for page analytics
Most interesting things are still experimental like defineModel and destruct props.
Yeah, I really like those!
destruct props. It is useless to use them, since they cannot be passed to hooks
not bad, dude
Hi! Do you have the code uploaded to a repository? could you share it? thank you!
Thank you! 🎉
It seems like Vue going to turn into react in a year or two, half of this new feature are what react already had in 2019 year and earlier
vue hype cycle - prefer stability
I still don't know how do a simple button wrapper in `Vue`. :(
Example... In react, I would just go `const Button = (props: JSX.IntrinsicAttributes['button'] & { myCustomPropTypes }) => `
I don't know how to do the same `JSX.IntrinsicAttributes['button']` in Vue.
This is actually much simpler in vue. Your Button Wrapper component will automatically inherit the attributes of its child button. Have a look at the fallthrough attributes guide in the vue docs.
If you want to be more explicit, there is also an interface called ButtonHTMLAttributes which is similar to JSX.IntrinsicAttributes['button']
About props in react it would be better to do HTMLAtributes for defining props
vue is acutally becomming react😂
Upgrading from vue2 to vue3 was a tragedy. never such a horrible stuff.
vue is combination between react and angular. I still like react more
how about a video without typescript
this $() and $$() and complex slots mechanics are really awful. i hope they simplify this at one point.
No worries, they did not go forward with that proposal!
Vue3 is starting to look like React which is BS cause I personally chose Vue cause it didn't look like React spaghetti code.
Changed everything again? I tired again and again rewrite my app
You don’t actually need it, just stick to certain version…
@@tsolanoff I stuck with version 2 because of broken backward compatibility. Spend a time learning how to migrate to version 3 and now need to spend a time again for learning how to migrate to version 3.3.
@@yatsuk the major part of all web apps are not being constantly updated just because they do their job. Migrating to new technologies requires many efforts and makes sense only if the current state can’t afford adding new features or supporting proper workability anymore. So as long as your app is working as it’s supposed to there is no need of migration. And you could develop your new projects using new version to follow up the tends.
Old syntax works as before, you don't need to rewrite anything
toy framework no one cares about.
Asians do, it's mainly for Asian market
does eslint support destructuring the props? i'm still seeing the error "...Destructuring the `props` will cause the value to lose reactivity.eslintvue/no-setup-props-destructure
..."
👍