it is extreamly easy as he explained

This is what we do with classes, but we take it a step further: components reference a controller, a controller can make use of 1 or more composables, depending on the case. Generally speaking, component-specific code sits in the controller class, and composables are used much like multi-inheritance or traits in other languages.

Yikes. So much time lost learning having to listen to someone with an ego... =\

you didn't pass any event how can you emit en event from the child that's not even passed?

This entire video is "custom text input with lots of functionality abstracted imto a highly reusable component is bad; use my highly abstracted form component that is the exact same thing." We're frontend devs, building custom inputs, forms, and state management is what we're suppose to be good at.

Bro, this tutorial was amazing!

I think the problem with Vue3 is that if they were just going to copy everything from react, which is the case with composables, they should have kept the original names as well, i.e. composables should be called React custom hooks.

very good video, thanks

I’m too sexist to watch this video lol

Thanks

Please don’t json stringify to then parse. Use structuredClone

another technical debt 😂

Amazing!

What happens if you want to change an icon globally? Like the checkbox icon

This incremental adoption is such a good thing. Currently with RC in React 19 npm packages are breaking left and right. It makes me not want to use React anymore.

what if we have a framework that doesn't require framework skills and just pure html and javascript and without build step?

So essentially what he is sayng is: We made something that doesn't work like there rest of the stuff that exist , because we think it looks cool, it's your fault, you are d|_|mb.

We use Nuxt 3 in production and it's amazing.

Really great library. I’m excited for these changes to prime react as I also use react at work and I’m trying to introduce prime react at work. These changes are a game changer. Congrats to the team. You all should feel very proud of the work you’ve done!

love love

is the number of npm downloads influenced by how difficult it is to work with node based environments?

Hiring managers are like NUMBER ONE PRIORITY make sure the person is brown, gay, has a vagina, and constantly mentions those things 1st and foremost.

What the data that we usually save to identify the face of particular user? I'm still confusing about the reference data that I should put on my database to checking whether the user is valid or not from their face.

one of the assets of Vue is his creator who speaks very well in english. On the other hand, i created a framework that doesn't require build step, with runtime type checks and coercion, auto reactivity in all variables except const 😂

What to use instead of index for keys? Fair to say “don’t use it”, but suggest what to do instead if it is such a malpractice…

Full of actionable items, thank you

Wow ❤

Thanks for the detailed presentation ❤

No native, no game. React ftw.

Great talk, great tips !👌

Yep, we did vue-property-decorator since our app was originally using GWT, and some of our devs really wanted to keep the Java/Class way of doing things.. And then when vue3 dropped support.. We couldn't do the slow migration over to vue3, so we pretty much did a DROP TOOLS and had 8 devs do Migration of over 5000+ files (not sure how many, Github only says 5000+), taken us 6 weeks and many of us doing WAY more than 16 hour days. Switching to Vue3-options-setup. Not full composition. Back when we did it, we didn't have access to `defineOptions` back then, and we needed it for a few select components, and we didn't wanna mix and match. There was a massive load of regular expressions run on each file, with a heafty amount of manual cleanup, (since regex can only do so much). Also wrote about 15 scripts that audited and reordering variable placements to ensure a standardise order of all Template Refs, Exposed methods, private method, internal data refs, any methods used soley for template events handlers, watchers, and then lifecycle hooks.. And ensured every component had them in that order.. We now have our own eslint rules to ensure we don't have any missing template refs, and that we don't have any extraneous template refs. We also ensure all template event handlers follow a set name convention. Our sister project actually jumped straight from GWT to Vue3 composition, but that was a re-write, not a migration. And they are taking advantage of things we couldn't.. Due to Vue2 lack of typescript support, all of our component properties were defined on a single "properties" objects.. not individually. And due to vue2's lack of handling reactivity when object properties were initialised with `undefined`, all our properties objects were classes, not simple objects.. and due to early design decisions, we are using 2-way databinding, which REALLY annoys me when wanting to what should be "easy features" turns into a data juggling nightmare for input data... And due to the size of the project, and the need for always adding even more features, we never get a chance to just DROP TOOLS and mass refactor anymore.. I mean, the last time we tried it, it taken 2 developers, a whole month, just to refactor our input validators to not require direct element access, but was able to understand delay loading 'refs'. Just so our project and our sister project could share a small component library.. This is while we have been forced to switch from cypress to playwright and moment to dayjs, and other whole project refactors just to keep things alive..

I wonder if the other 3 people who also used class components also had the same frustrations

More showing, less talking is what I prefer.

great presentation

I'm just moving back to Laravel tbh. Still love Vue for the frontend though.

To continue watching this course, head over to 👉 www.vuemastery.com/courses/nuxt-authentication/

Love love love this format. Thanks so much Adam.

Thanks @danielkelly ❤

This video was super clear and helpful thank you!

amazing.

I don't see any useful info here, just ad, so sad

I prefer custom input components using VeeValidate and Yup/Zod. FormKit looks similar but it does not have advanced headless form components for free.

That was funny 😂

you explained it very well

but does formik look different in the background? :D

nuxt is not stable as next i tried both but DX so much better on next

Pinia is so easy , l am new to Vue,not worked with vuex but I found pinia very friendly and easy to use for state management

guys upload vue tips and tricks,best approaches

Scalable forms? Easy! form:hover > * { scale: 1.5; transition: scale 1s linear; }

I’m impressed this actually seems like a good solution. I might try using it in my next project.