Then once built, the previously _unrefs are transformed into vue.unref, which is correct and makes the app work again.
Now, this is the first time really diving into the vue core, so I might have been looking at the wrong thing, but I did some digging and found a couple things.
bug was introduced after 3.2.26
it only happens for me when I don't import computed and use it.
logging ast before and after this transform call to check what the difference is, I found that the UNREF symbol was missing from the helpers property when I did not import computed
Looking even further I found the UNREF helper symbol was being added when computed was imported during thistraverseNode call.
This is as far as I got for my case. I look into the traverseNode code, but couldn't find anything glaring at me that could be causing it. It does loop thru the transformNodes tho, so I am going to assume something is going wrong within those calls.
Looking at the possible transformers being run, the only one that caught my eye was ssrInjectCssVars, but again I am not currently seeing anything glaring at me that could be wrong.
Link to minimal reproduction
Steps to reproduce
Open link, make sure its on PROD with SSR ON. Near line 20 in SSR tab we have an
_unrefcall. But it isn't imported first.
What is expected?
For build to succeed. (
_unrefto be imported from
vueprior to its call.)
What is actually happening?
_unrefis not defined
Any additional comments?
@skirtles-code observed that it's not just
computed, anything deemed
setup-maybe-refwill fall into the same problem:
The text was updated successfully, but these errors were encountered: