Repository navigation
vue: a template tag for a .vue or defineComponent component never links to that component #1743
Description
Symptom: in a Vue single-file component, a template tag that renders another component (<Child/>, <my-widget>) never links to that component when the binding is a .vue default import or a defineComponent(...) value — which is how Vue components are written. On two real Vue apps, 0 of 1,692 component tags resolved (all ambiguous_unknown); only a tag naming a plain function resolves.
Repro
<!-- src/views/Parent.vue -->
<script setup lang="ts">
import Child from '../components/Child.vue';
</script>
<template><Child /></template><!-- src/components/Child.vue -->
<script setup lang="ts">
function childLocal(): string { return 'c'; }
</script>
<template><b>{{ childLocal() }}</b></template>axiomcode index, then axiomcode path src/views/Parent.vue:4 childLocal
Expected: the tag at Parent.vue:4 reaches Child.vue (its module / setup), so impact on Child's code names Parent.
Actual: no chain of resolved calls connects …; the Child site is ambiguous_unknown; impact 'Child.<module>' has no users.
Activity
swapnilpaliwal-sd commentedon Sep 29, 2026
This issue now tracks 3 related issues about Vue single-file components: script blocks, template tags and freshness (#1744, #1745, #1761). Those issues are closed as duplicates of this one; each keeps its own description and reproduction. The group is fixed together in one change, and this issue closes when that change reaches the release branch.
swapnilpaliwal-sd commentedon Sep 29, 2026
Fixed by #1754 (merged into 0.1.8).
swapnilpaliwal-sd commentedon Sep 29, 2026
Fixed by #1754 (merged into 0.1.8).