Skip to content

vue: editing a .vue file leaves the graph 'up to date' and queries answer from the old text #1744

Closed as duplicate

Description

@swapnilpaliwal-sd

Symptom: after editing a .vue component, axiomcode index (and the background refresh) report graph up to date, and queries keep answering from the old text. .vue files are indexed but never recorded in the graph's file table, so an edit to one is invisible. Seen for both a JavaScript and a TypeScript component.

Repro

src/lib.js:        export function lazyHelper() {}  export function newHelper() {}
src/router.js:     export const routes = [{ component: () => import('./views/Home.vue') }];
src/views/Home.vue:
  <script setup>import { lazyHelper, newHelper } from '../lib.js';</script>
  <template><span>{{ lazyHelper() }}</span></template>
  1. axiomcode index
  2. edit Home.vue's template to {{ lazyHelper() }}{{ newHelper() }}
  3. axiomcode index → graph up to date; axiomcode impact newHelper → no users

Expected: the edit is detected and the graph rebuilt; impact newHelper names Home.vue:4.
Actual: stale graph presented as current (.axiomcode/out/files.json lists no .vue file).

Activity

  1. swapnilpaliwal-sd commented on Sep 29, 2026

    @swapnilpaliwal-sd
    ContributorAuthor

    Consolidated into #1743, which tracks this issue together with related ones about Vue single-file components: script blocks, template tags and freshness. The description and reproduction here still apply, and the fix for the group covers them.

  2. added a commit that references this issue on Sep 29, 2026
    2150e2c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugSomething isn't workingengineResolution / call-graph engine rulesjavascriptJavaScripttypescriptTypeScript

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions