This is the result of hard work. SFCs in the editor is complicated.
Devs like @johnsoncodehk.bsky.social put up their hand to take on these tedious complexities, saving us immense time and headaches.
Forever grateful 💚
This is the result of hard work. SFCs in the editor is complicated.
Devs like @johnsoncodehk.bsky.social put up their hand to take on these tedious complexities, saving us immense time and headaches.
Forever grateful 💚
Thank you SO MUCH @johnsoncodehk.bsky.social for all your hard work.
@vuejs.org devs, it's hard to overstate what Johnson has done to make our lives better.
Everytime you ctrl + click a component, get auto complete for slots, see red squiggles for missing props, use defineProps or defineEmits etc
MASSIVE @vscode.dev discovery!
...might be an exageration.
while searching for files, you can press "@" to start looking for symbols before even entering the file!!!
1. ctrl + shift + p
2. start searching
3. don't press just enter yet!
4. type "@" and start searching for a symbol
It's 1:30am, I've been writing @vuejs.org and @laravel.com code all day, and I couldn't be happier.
I love these frameworks. They make my job a joy 💚🧡
I'm not sure that's exactly what they mean.
A good example would be the Ukraine flag. Showing support on your social account vs a GitHub project/docs etc.
It's so crazy to me how easy it is to swap components out using slots with @vuejs.org.
For some reason, feels like something like that should be difficult but it's not.
It means many of my components can do LOADS of work building themselves, with zero flexibility sacrafice.
There's many places in UIs I wish "time ago" was used instead of a date.
Dates often don't mean anything to me at a glance... especially when working with recent data.
@vueuse.org Is a wonderful thing!
For me, it's the most important part of the @vuejs.org ecosystem. The reason is 50/50.
- 50% having solutions to an enormous number of problems I face day to day
- 50% learning good practices to build my own composables
💚
We're thrilled to announce the first stable release of Oxlint - version 1.0!
Our Rust-powered JavaScript/TypeScript linter delivers 50~100x faster performance than ESLint with 500+ rules and zero configuration required.
Time to give it a try!
voidzero.dev/posts/announ...
Anyone else visit the @vueuse.org docs more than the @vuejs.org docs?
This is crazy exciting!!!
Can't believe how quickly this is all happening 🚀💚
Love your perspective here!
Making sure things are documented in the right context 💚
That second one is nuanced.
I was using quasars QTable component. It has sorting built in. I could have sorted in the parent, but then I lose the UI that QTable provides (little arrow when clicking on the header)
When needing the sorted rows, using the computed on the component was just easier.
There are two use cases I can remember.
1. telling a form to validate (someFormComponent.value.validate())
2. accessing rows from a table - where the table has sorting internally - to avoid sorting those rows a second time
Yes but rarely.
Perhaps it should be mentioned with the useTemplateRef helper in the docs? The two go hand in hand.
vuejs.org/api/composit...
Oh woooow! Just discovered "satisfies" in typescript.
And that's why we love you!
Hopefully this means I'm close 😐
Biggest mistakes I've made...
- organizing code by type
- not embracing typescript sooner
- taking DRY waaaay too far
Looking back, correcting those mistakes has been a satisfying part of my career!
Could someone explain to me what is meant by "React has a more robust ecosystem"?
More people hiring for React? More packages? More problems solved?
For me Vue is by far a better experience than React, and it feels like there's nothing I can't do.
What's the React ecosystem I'm missing out on?
When you expose an array of callbacks, and some of them can be promises, do you run those callbacks in parallel? Or do you use await and run them one at a time?
I've been doing parallel, thinking the user can just pass a promise with their own await within if that's what they desire.
Haven't had a single problem with tsdown (Thanks @voidzero.dev!!!)
Going to move all the packages I'm working on to tsdown 💪
I need to get into the habit of using @vuejs.org devtools more often to find files.
It's insanely helpful! Especially when you're tired and just need to find the dang file 😅
I feel like it's really easy to stay up to date with tech these days.
I've chosen my stack. @laravel.com, @vuejs.org and Quasar.
I could take Luke from 5 years ago, drop him to now, and he'd be productive in days.
Yea, this drives me nuts.
Threads are great when there's a lot of people, but for one-on-one chats it's kinda silly.
@pi0.io What's faster. Pressing "Enter" on the command line or running "obuild src/index.ts"?
I can't tell.
Just tried obuild. It was so fast, I thought it was broken 😲
Using it to speed up feedback in Dev, then build with unbuild. Has worked flawlessly so far!!!
@unjs.io is awesome!
great to hear @pi0.io is working on something with rolldown. Not sure I've ever been this excited about the js ecosystem 😱
It feels like a million exciting things are about to happen all at once!
Whoa!!!
I'd never even heard of tsdown.
I put off writing typescript packages for years because it's always been so complicated, and defaults seem to change daily.
Would be curious to know the main difference between tsdown and unbuild 🤔
Oh sweet, thankyou!
Curious to hear everyones experience with $ref!