ComputedRef generated in setup function no longer has `.value` stripped off it's type in template

[yankeeinlondon]

After coming back to a repo that had been working fine I now find that when define a reactive object with this strongly typed function:

and then pass s as return value in setup. The template incorrectly reports missing properties that in fact do exist at runtime:

in all cases the error on the template hover follows this pattern:

Property 'wrapper' does not exist on type 'ComputedRef<Record<"root" | "wrapper" | "input" | "info" | "warn" | "error" | "inputControl" | "inputRow", string>>'

My expectation would be that a ComputedRef defined in the setup() function would have the .value stripped off it for type checking in the template. That is correct, right? I mean it does work so clearly VueJS is stripping off the .value.

[johnsoncodehk]

Maybe same with #322. Please try delete yarn.lock / package-lock.json and node_modules, and then reinstall it.

[yankeeinlondon]

Yes I think this is a DUP. Will close.