When You SHOULDN'T Use Computed in Vue

RESOURCES

Get early access to videos, exclusive content, interactive code challenges, and more.

follow me on twitter:

MUSIC
#vuejs #vue #javascript #webdev
00:00 Introduction
00:22 Credit
00:33 Two things about computed
01:24 When could this be bad?
02:25 The solution - eager computed properties

[RomanDawydkin]

Note: it's all changed in Vue 3.4: "a substantial refactor of the reactivity system, with the goal of improving re-compute efficiency of computed properties". "With the post-3.4 optimizations, the callback now only fires if the computed result has actually changed."

[fredhair]

I think the real issue you highlighted is unnecessarily using a computed value as a dependency on another computed value!

[dCoder]

Since vue 3 i struggle when to use composable and when not.
Like everything could be outsourced in a composable (every api request, every state change etc.).
It is very confusing... 🤕

Like 80% my logic is in composables...
Is there any tip or video that could help?

[dbroche]

thank you for sharing all the great stuff!

[pawankumarthakur]

Could you share the Theme name, please? Looks really nice.

[abdallah.s]

Thank you for this valuable information

[jameswrightson]

"When You SHOULDN'T Use Computed in Vue" - "In a few cases"

[dominikpolak]

This is outdated. Can't replicate it on Vue 3.5

[Linkplay]

just do $: expensiveCalculation(count) and you will be good
keep calm and use svelte