I've started sharing my content on Threads, been experimenting with AI chatbots, but unfortunately, made no progress on my blog post about optimistic updates.
In this issue, enjoy the latest articles, videos, and tools to keep your Vue and Nuxt skills sharp!
👉🏻 In benchmarks of server-side rendering (SSR) across frontend frameworks, like React, Vue, Svelte, and Solid, fastify-html and Vue are the top performers.
As you can see in the example above, the ref can only be accessed after the component is mounted. Therefore, we use the onMountedonMounted lifecycle hook to focus on the input element. In a template expression, myInputmyInput will be nullnull on the first render because the element doesn't exist at that point.
If the auto-inference doesn't work as expected, you can provide a type argument to useTemplateRef()useTemplateRef() to specify the type explicitly:
👉🏻 This book is a collection of common and challenging trouble spots that trip up JS and TypeScript developers, along with tips on how to recognize and resolve them.
👉🏻 The Temporal API in JavaScript offers a new approach to handling time with the Temporal.ZonedDateTime object, which accurately represents dates and times with their corresponding time zones.
👉🏻 A CLI tool that detects memory leaks in web applications by simulating user interactions, analyzing heap snapshots, and identifying leaked objects, event listeners, and DOM nodes.
😂 Fun
🔗 Want more Vue & Nuxt content?
More Exclusive Vue Tips: Join Michael Thiessen's newsletter and get great Vue tips and insights delivered to your inbox each week.
Weekly Vue & Nuxt Videos: You must subscribe Alexander Lichter's YouTube channel if you are interested in Vue & Nuxt.
DejaVue Podcast: A weekly podcast about Vue.js and the ecosystem around it.
Comments? Join the discussion about this issue in our Discord community.
Sunday, January 5, 2025 Update: Bluesky images work again and thus the Great Art on Bluesky channel is back. If you're on Bluesky please subscribe. # The crazy thing about Bluesky's API is they took already standardized things like links and enclosures, and after 20+ years came up with new definitions. Makes our apps more expensive to maintain, and we waste time and human wear and tear on stupid bullshit make-work. Developers are people, and our work is already horribly overly complex, we're working at the edge of comprehension, and what the fukc let's throw some more unnecessary complication into the mix. Arrogance, narcissism, whatever the source is, it's not a good way to introduce yourself. And, even better, after you go through the maze they break it, with an error message about legacy blob bullshit. They've already done this, and they're just getting started. It's why I say they should just adapt to RSS instead of trying to forc...
评论
发表评论