Weekly Vue News - #58 - Writeable Computed Property

Migrated Issue

Expect missing links and broken styling, as this issue has been migrated from my previous newsletter service.

Hi 👋
First testers are testing my code snippet tool and I'm currently migrating the code to Nuxt 3, as I need server routes for Paddle payment integration.
Below you see an image of the current editor which I used to create the code snippet image for this newsletter.
Have a great week ☀️

Vue Tip: Writeable Computed Property

Computed properties are by default getter-only.

If you attempt to assign a new value to a computed property, you will receive a runtime warning.

In the rare cases where you need a "writable" computed property, you can create one by providing both a getter and a setter:

Now when you run this.fullName = 'John Doe', the setter will be invoked and this.firstName and this.lastName will be updated accordingly.

Curated Vue Content

📕 Make a Nuxt.js Clone with Vue 3 and Vite

👉🏻 This article will be useful for those who want to write an application with Custom Server Side Rendering and want to learn more about how it works under the hood.

Quote of the Week

Curated Web Development Content

📕 Default Exports in JavaScript Modules Are Terrible

👉🏻 JS modules have two ways to define an export: default exports and named exports.

👉🏻 This article explains why default exports are a poor practice and lead to a worse developer experience.

📕 Infinite Scrolling: When to Use It, When to Avoid It

👉🏻 “Infinite scrolling minimizes interaction costs and increases user engagement, but it isn’t a good fit for every website. For some, pagination or a Load More button will be a better solution.”

📕 Research: quantifying GitHub Copilot’s impact on developer productivity and happiness — github.blog