Thanks so much for this great overview! I did some Vue 2 code, and then I opened up someone else's program with some of the Vue 3 features in it (I didn't even know it at first). I saw this Ref and unrefs everywhere and was like wtf is this! Your video saved me hours of pounding my head against the wall figuring out this code.
Wow thanks you made me discover that we can use a "setup" script tag instead of a setup function for single file components 😮. I learned Vue one week ago, begining with the Options API, then switching to the Composition API, learning about class based components and now about setup script tags... That's kind of overwhelming and hard to know what's the most recent recommended way of writing a Vue app. 😅
did any one of the developers at vue stop for a second to think that people who use vue in their job might not be willing to relearn the same crap over and over again? i am currently unable to get a piece of text from the data i fetched because of this ref bs.
I'm building a simple blog app with interactions (like,dislike, share). But I get inconsistent count on the template. I'm using sessions for anonymous users. I want to display total interactions across users but when I refresh what I get is count for that session? Any guidance?
This all seems very promising and your video is pretty clear. BUT, please make a video working with real case reactive & ref objects. 'Cause there's a lots of weird situations like:: Having an empty ref obj and the assigning to it a few props, or dealing with arrays is quite a maze. I've most likely always ended up using ref. Otherwise is creates weird references between component state and pinia for example Thanks for the content!
Summing up: "Reassigning objects is possbile with Ref." That means you can destructure an object into a reactive REF one and bulk in there the props with it's values. Also alows to add new ones!
Hello Erik. great video and thanks for sharing. but one question..i see there seem to be massive change in the script block..no setting of variables on a data function etc it is just straight variables and functions like in Svelte..is that the new paradigm?
i really dont understand why they change so much from vue 2 to vue 3, i know we can stil program like vue 2 in vue 3, but i woudl like to know what is the improvement at the cost of not doing things straigforward like in vue 2?
yeah... trying to think of it myself too. My best guess/shot is - monetization. Eventually, vue3/4 will not support Options API. Apps built on Option API will come to end-of-life and from here - either invest in extended support for security reasons or invest in rebuilt/refactoring/migration to new structure of Composition API.
Hey Erik, thanks for the video! I want to ask a question. In Options API we could predefine our (in a lack of a better term) object model in data object. Like this: data: { task: { name: null, status: null } } And then fetch it from backend and fill those null's. So, when you define in your template task.name you don't have to check out if a task object exists. How should I do this in Composition API? Right now I figured out one option, which is not the best in my opinion: Predefine it like this: task = reactive({ name: null, status: null }) and then, in my getTask function, manually assign each of the properties (task.name = data.name, etc). Oh, UA-cam isn't the best place to ask a code questions lol.
I also curious how to properly set watchers in this case, if I want to watch changes in task object. Previously did it with deep: true, what about new API?
Hi Eric, I would like to tell you that there is probably a collision or some kind of error when two times the word ref is imported. I am thinking of importing ref from "firebebase/database" and "vue".... have you ever encountered such a situation? I will probably have to separate a certain piece of code into a separate file
Hey Erik, can this be done with a vanilla JavaScript class object? I am currently attempting to use a custom class with Vue 3's reactive and it's not keeping the object's property values. Cheers!
Wait, I didnt know you could get away with using your refs in the template without returning them first? I didn't like the composition API, because of how much I had to import things, or type extra, or worry about how I'm going to organize all the code. Do you think everyone should use the composition API? Or am I okay with sticking with the options API
You can install a package called 'unplugin-auto-import' and you no longer have to import anything which is super convenient. For me, about the code organization, I just put the same type of objects together much like in the options API. All the refs, consts, computeds, functions, etc stick together in their predefined sections.
He is using script setup which is a syntactic sugar for setup function. In this syntax, you don't have to return refs, computed etc. and you even don't have to register the components. Anything specified at top level becomes automatically available in the template, which allows you to write lesser boiler plate code.
Just a suggestion, you can tell more VS code shortcuts that you uses, like line delete, comment line, etc. I can search, but it will be more helpful to see what you are using and where, instead of reading about shortcuts.
No, vue 3 offers additional features like teleport, suspense components, fragments (ability to write multiple root elements in a component), support for multiple v-models on same component, a proxy based reactivity system that removed the caveats we had in vue 2, concept of having multiple isolated vue apps in a single project and a couple of minor breaking changes.
So unfortunately Vue is becoming more and more like React. I don't understand why you always have to complicate things that work well. It was already like that with Angular and now Vue is making the same mistake. Too bad. I will work as long as possible with Vue v2, it is fast, efficient and uncomplicated. Exactly what most developers want.
I thought Vue was supposed to be "easier" to use than React. But if Vue is gonna become more complicated than it has known to be and tries to be like React, then I might as well just use React and not even think about Vue at all.
It is too much strange to put Javascript code inside a string or double curl braces, both are JS code, there is no reason to put one inside double curl braces and other inside strings, they should change this, both React and Svelte do this the right way, using one curl brace for everything that is Javascript inside the template, doesn't matter if it is a children or an attribute
You are the best man, I can't describe my gratitude for your easy explanation
Thanks so much for this great overview! I did some Vue 2 code, and then I opened up someone else's program with some of the Vue 3 features in it (I didn't even know it at first). I saw this Ref and unrefs everywhere and was like wtf is this! Your video saved me hours of pounding my head against the wall figuring out this code.
Your skills in Vuejs are awesome.
Tanks for explaining this methods so well ❤❤
My pleasure 😊
Hey erik thank you because of you i found out vue and it's my favorite framework
I will soon be making Vue tutorials on my channel 😊
Vue’s weakness is there’s too many ways to do the same thing.
Wow thanks you made me discover that we can use a "setup" script tag instead of a setup function for single file components 😮. I learned Vue one week ago, begining with the Options API, then switching to the Composition API, learning about class based components and now about setup script tags... That's kind of overwhelming and hard to know what's the most recent recommended way of writing a Vue app. 😅
Go with vue 3 script setup
We discovered a new type of cube which sides are not equal to each other 😂
hahah! That's a good point!
This is great stuff! Custom refs example was gold
did any one of the developers at vue stop for a second to think that people who use vue in their job might not be willing to relearn the same crap over and over again? i am currently unable to get a piece of text from the data i fetched because of this ref bs.
I'm building a simple blog app with interactions (like,dislike, share). But I get inconsistent count on the template. I'm using sessions for anonymous users. I want to display total interactions across users but when I refresh what I get is count for that session? Any guidance?
so even if use toRefs(cube) to manipulate values i haves to use length.value, width.value etc?
great explanation, thanks!
Glad it was helpful!
hi, When would I ever use toRef or toRefs?
Thanks for making such great 👍 tutorials
Question, how to use nodejs server in Vue Vite bundler.
This all seems very promising and your video is pretty clear. BUT, please make a video working with real case reactive & ref objects. 'Cause there's a lots of weird situations like::
Having an empty ref obj and the assigning to it a few props, or dealing with arrays is quite a maze. I've most likely always ended up using ref. Otherwise is creates weird references between component state and pinia for example
Thanks for the content!
Summing up: "Reassigning objects is possbile with Ref."
That means you can destructure an object into a reactive REF one and bulk in there the props with it's values. Also alows to add new ones!
Other great video!! Thanks Erik!
Hello Erik. great video and thanks for sharing.
but one question..i see there seem to be massive change in the script block..no setting of variables on a data function etc it is just straight variables and functions like in Svelte..is that the new paradigm?
Yes! It's a lot like Svelte in that regards. You still need to surround reactive variables though with ref or reactive.
@@ProgramWithErik snap! this is amazing! Thanks!
Hey Eric,
I have a problem. I just want to make a global variable isLoggedIn, that i can change to "true" or null. How can I do this?
Nice video,
i really dont understand why they change so much from vue 2 to vue 3, i know we can stil program like vue 2 in vue 3, but i woudl like to know what is the improvement at the cost of not doing things
straigforward like in vue 2?
yeah... trying to think of it myself too. My best guess/shot is - monetization. Eventually, vue3/4 will not support Options API. Apps built on Option API will come to end-of-life and from here - either invest in extended support for security reasons or invest in rebuilt/refactoring/migration to new structure of Composition API.
Hi, nice vid.
How did you make those auto-comments in VS code ? Is there any command? Or is just an extension?
Win: Ctrl + /
Mac: Cmd + /
Hey Erik, thanks for the video!
I want to ask a question. In Options API we could predefine our (in a lack of a better term) object model in data object.
Like this:
data: { task: { name: null, status: null } }
And then fetch it from backend and fill those null's. So, when you define in your template task.name you don't have to check out if a task object exists. How should I do this in Composition API?
Right now I figured out one option, which is not the best in my opinion:
Predefine it like this: task = reactive({ name: null, status: null }) and then, in my getTask function, manually assign each of the properties (task.name = data.name, etc).
Oh, UA-cam isn't the best place to ask a code questions lol.
I also curious how to properly set watchers in this case, if I want to watch changes in task object. Previously did it with deep: true, what about new API?
Thanks!
Hi Eric, I would like to tell you that there is probably a collision or some kind of error when two times the word ref is imported. I am thinking of importing ref from "firebebase/database" and "vue"....
have you ever encountered such a situation? I will probably have to separate a certain piece of code into a separate file
Hey Erik, can this be done with a vanilla JavaScript class object?
I am currently attempting to use a custom class with Vue 3's reactive and it's not keeping the object's property values.
Cheers!
I think its can we mimic this, using event mutation observer.
Wait, I didnt know you could get away with using your refs in the template without returning them first? I didn't like the composition API, because of how much I had to import things, or type extra, or worry about how I'm going to organize all the code. Do you think everyone should use the composition API? Or am I okay with sticking with the options API
Use what you want to use.
Options API or Composition API (setup() {} or )
You can install a package called 'unplugin-auto-import' and you no longer have to import anything which is super convenient. For me, about the code organization, I just put the same type of objects together much like in the options API. All the refs, consts, computeds, functions, etc stick together in their predefined sections.
@@spyxd5245 I'll install it and see if it helps me transition for bigger projects
He is using script setup which is a syntactic sugar for setup function. In this syntax, you don't have to return refs, computed etc. and you even don't have to register the components.
Anything specified at top level becomes automatically available in the template, which allows you to write lesser boiler plate code.
@@blank4157 Yeah all of a sudden now i like the composition api hahaha
Feel like sometime you write some codes because you have it on your other screen instead of explaining the actual "why" and "how it work"
Please help me, how to use trigger click button in setup() method in vue 3 (Vue 2 i used this.$refs in methods, but Composition API I can't)
Check out the button example with template refs in the video!
I will soon be making Vue js tutorials
Is Vue still simpler than React to learn?
nice ^) thanks
so fast, this tutorial is even more confusing than vue it self
Just a suggestion, you can tell more VS code shortcuts that you uses, like line delete, comment line, etc. I can search, but it will be more helpful to see what you are using and where, instead of reading about shortcuts.
Thanks for the tip! I'm using VIm extension with VSCode, and I know some of the shortcuts, but I can probably learn a few more
Is Vue 3 essentially Vue 2 + Composition API ?
No, vue 3 offers additional features like teleport, suspense components, fragments (ability to write multiple root elements in a component), support for multiple v-models on same component, a proxy based reactivity system that removed the caveats we had in vue 2, concept of having multiple isolated vue apps in a single project and a couple of minor breaking changes.
That's a good summary!
This reactivity feature very useful in Vue JS 3
Yup!
Made awesome Vue2 then complicate it, and it's Vue3.
How do you type so dam fast, and move so fast
So unfortunately Vue is becoming more and more like React. I don't understand why you always have to complicate things that work well. It was already like that with Angular and now Vue is making the same mistake. Too bad. I will work as long as possible with Vue v2, it is fast, efficient and uncomplicated. Exactly what most developers want.
You can still use vue 3 with options API, it's not like the options API is gone for good, it's still supported and works the same as in vue 2.
i cannot agree more
// According to the #Vue2 docs, this should be 1
// According to the #Vue3 docs, this should be 2
// They are both wrong! ⚡ 😂 ❤️
What should be #1?
If you use options api it is reactive out of the box
well, apparently they have put extra effort into making it as confusing as possible LOL
How about to make changes reactive from pure js?
1. Get element by ID
2. Change its value
3. This will update vdom?
I thought Vue was supposed to be "easier" to use than React. But if Vue is gonna become more complicated than it has known to be and tries to be like React, then I might as well just use React and not even think about Vue at all.
There are times when you need to use the API, but otherwise, just leave it to vue js to handle.
Now I know how to make a cube: 10x20x33 …. Repeat after me, that’s a cube.
BRB… going under shower crying 😭
It is too much strange to put Javascript code inside a string or double curl braces, both are JS code, there is no reason to put one inside double curl braces and other inside strings, they should change this, both React and Svelte do this the right way, using one curl brace for everything that is Javascript inside the template, doesn't matter if it is a children or an attribute
that's not a cube
Yeah lol
@@ProgramWithErik hahaha
anyway nice video
why do you use composition api every time? It's purely additive. Read the docs. I think you are low competence developer
docs says that it's not a good practice mix option with composition API. I don't see the problem of using composition API every time