Vue.js 3.0 Composition API Tutorial in 15 minutes 

Same

It only makes sense when the components get really large.

this. only new syntax was shown, nothing much

because it's like Erik doesn't know what it is he just know how its implemented and that how basically all tutorials are like ...pretty shallow

Also, when returning repos data from github api, he says "gh has rate limiting" because it's returning 30 entries at a time. It will have rate limiting, but that was pagination. SMH.

Thanks

Node, as in Node.js is a server-side language. Not sure where the issue lies.

@@demonicious_ this is completely wrong statement. "Node.js® is a JavaScript runtime built on Chrome's V8 JavaScript engine." It's runtime for JS, not the different language.

Thanks for pointing this out. I was looking for a comment like this to upvote it. Node.js to Javascript is what Java VM is to Java.

My understanding is that it is meant to be beneficial when creating large applications. I don't there is a benefit for small demo apps. One cool thing about Vue 3 is the ability to make data non-reactive. Previously with Vue any data properties were reactive, which has an overhead if that data doesn't need to be.

add before or after the {{your_data}}

Glad you like it!

@@ProgramWithErik, yeah and now I have to buy one in Iran with all these sanctions (from us) and hard times in economic problems! :-D jokes aside thank you for your content.

I wanted to illustrate how the watch function can be triggered when any reactive variable changes. For example we could use the same watch function if the username was coming from a prop. Or maybe another function changed the user name, the watch would still be triggered.

Thanks it's a Corsair k70 keyboard. But half the people hate the clicking so I use my non clicky keyboard in my videos now. (Well not as clicky)

@@ProgramWithErik Thank you

Yes! I’m selling the recoding here! Course.vue course.vuecourse.tech/vue3

@@ProgramWithErik thx, you should update in the video description

Thanks for the feedback Alisha! Yes, I created the other variable so I could use the watch function. This was to illustrate that when any reactive variable inside the watch function changes the whole watch function gets triggered again. You are right I could have put the fetch in it's own regular method, but that would miss the point. Let's say for example the username came not from an input, but from a prop being passed down. In that case you'd have to have some sort of dynamic way of having the fetch re-trigger. That's the power of watch. Also ref and reactive are very similar. The way I like to think about it is, I use reactive for objects and ref for simpler items like booleans, or integers, but I need them to be reactive. You could use Reactive for everything if you wanted too...

Thanks for watching

I really like VScode

It's still in a release candidate...

Synthwave 84

Russ Painter correct

@@ProgramWithErik how is that a good thing? Those effects will be running any time anything changes. And that code could be making api callls!! Isn't there a way like in v2 to have watchers be for specified property?

@@RussPainter8 i think variables that use ref() and reactive() will be watched only. A better solution would be to add a function to the click event to search for users.

It's a simple example, I think it does

That's technically true. Node is JavaScript run time. Next time I'll be more explicit

I still have it! I just didn't turn it on

Which questions?

@@ProgramWithErik Actually... just about every question one can have regarding the composition API, except maybe the syntax (partially). I was really hoping to see some explanation of _why_ this new API exists. Instead, you showed a code example that would look much better with the options API. That kind of makes the problem many people are having with this API worse.

You realise it’s optional?

Also, there are use cases where it makes a lot of sense - for reuse for example.