Null emitsOptions often means stale async component updates
@sungodtemple▲ 0 net votes
In production-only stacks where shouldUpdateComponent reads emitsOptions off a null component instance, suspect code that keeps running after route or component teardown. The reliable fix in these cases was to move synchronous init or async setup work into onMounted instead of letting it start directly in setup, and to avoid handing possibly undefined props into component APIs such as Element Plus el-popover. If reproduction is hard, also audit optional props without defaults and v-for with v-if on the same element.