The week after next, I'm on vacation, so I'm busy preparing the following two newsletter issues for you. Enjoy this issue with many interesting articles, videos, tips, and more.
👉🏻 This article will guide you through setting up Vue Router, the official routing engine for Vue.js, to create a seamless navigation experience in your Vue.js project.
👉🏻 shallowRef is a great utility in Vue.js that could help improve performance of your website if you are dealing with huge data structures like nested objects or arrays.
Unlock 48 hours of free access to Vue.js Developer Certification Training on June 29 & 30, 2024.
Dive into theory, coding challenges, quizzes, and a mock exam to gauge your readiness for the official certification.
🔥 Vue Tip: Cache Component Instances With the KeepAlive Component
KeepAliveKeepAlive is a built-in Vue component that allows you to conditionally cache component instances when dynamically switching between multiple components.
Let's take a look at a simple example to understand how KeepAliveKeepAlive works. We have two components, ComponentAComponentA and ComponentBComponentB, and we want to cache the instances of these components when switching between them.
1<script setup>2import { shallowRef } from 'vue';3import ComponentA from './components/ComponentA.vue';4import ComponentB from './components/ComponentB.vue';56const current = shallowRef(ComponentA);7</script>89<template>10 <div>11 <label12 ><input type="radio" v-model="current" :value="ComponentA" /> A</label13 >14 <label15 ><input type="radio" v-model="current" :value="ComponentB" /> B</label16 >17 </div>18 <component :is="current"></component>19</template>
If you switch between the components using the radio buttons, you will notice that the component instances are destroyed and recreated every time you switch between them. Thus, the state of each component is lost.
If you want to cache the instances of the components, you can wrap the componentscomponents element with the KeepAliveKeepAlive component.
👉🏻 A Chrome extension to measure and analyze page elements.
👉🏻 Once enabled, it lets you hover over elements to view info similar to DevTools (padding, margin, etc.) with the added ability to measure specific distances on the page.
How's it going? I was planning to release the update for Reusable Components yesterday, but things haven't gone as planned. Instead, I will be launching it next week. I need a just a bit more time to make sure that the quality is up to my standards. As I've been updating the course and re-writing all the content and step-by-step refactorings, I've also been able to simplify a few things. It's just like refactoring a piece of code, and it's one of the greatest feelings. I also looked at how much content is in there, and it looks like it will be similar to the Clean Components Toolkit. Lots of great content on how to write highly reusable components, simplified and updated — I can't wait to release the update next week! Oh, and one more thing: I'm doing a podcast with Alex Lichter ! It's called Deja Vue and we'll be releasing the first ...
Monday, November 20, 2023 I'd pay $10K up front # Matt Mullenweg : "Sales of the 100-year plan so far: 0. Hundreds of people filled out the form, though. I think we really messed something up in the follow-up, including not making it self-serve to start. Will review and try again. It's an important promise to us." # I'm very much a customer for this service. It would be worth $10K for to buy 100 years of persistence for my web writing. A simple easy to understand service that helps get the process started. # I transfer scripting.com to Automattic as registrar. # I upload the contents from S3 to Automattic server. Static files, HTML, feeds, images, code. # Automattic provides an API to keep the files updated and so I can add to them as long as I'm still writing. # The files are publicly accessible over HTTP. # Automattic agrees to renew the domain for 100 years, and manage access to the files, with reasona...
评论
发表评论