Improve the display text on computed values that are not accessed.

[NHZEX]

I encountered an issue where a computed property shows as undefined in the Vue Devtools when it's not used in the template. This behavior is confusing and can make debugging more difficult.

Preview: https://stackblitz.com/edit/vitejs-vite-md6fq8?file=src%2Fcomponents%2FHelloWorld.vue

[alexzhang1030]

This is a vue design pattern. Computers are lazy, we will never know its value until somewhere access computedValue.value. See computed implementation

[alexzhang1030]

We can improve the display text on computed values that are not accessed.

[NHZEX]

We can improve the display text on computed values that are not accessed.

Is it possible to provide a feature in devtools that actively triggers the computation of these values?

[alexzhang1030]

We can improve the display text on computed values that are not accessed.

Is it possible to provide a feature in devtools that actively triggers the computation of these values?

I would not recommend doing it. Access value will make devtools the computed values' dependency, which will mess up the reactivity system and introduce some perf issues.

In the future, we might make this as a devtools plugin.

[victorgarciaesgi]

Hello! I have the same problem on a lib i'm making. Didn't know it was by design

[victorgarciaesgi]

Maybe add a button next to the computed like Reveal value to avoid unwrapping all properties?
That way it's opt-in