Vue <script setup> calls to Nuxt auto-imported composables aren't linked
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 40/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- nuxt, typescript
- Domain
- devtools
Research direction
Start by reproducing the gap with a small Nuxt project: an auto-imported composable such as usePermissions called from both a .ts file and a .vue <script setup>, then run codegraph callers usePermissions and compare the two lists. The issue does not name the source files that resolve calls, so first find where codegraph resolves auto-imported names for .vue files. Done when the .vue callers appear alongside the .ts ones, and the explicit-import case still works.
Written by the indexing model from the issue text.
Description
Version: codegraph 1.6.2, macOS arm64 (bundled runtime)
Project: Nuxt 4 SPA (srcDir: app/) in a pnpm monorepo, with composables auto-imported from app/composables/ and a few extra imports.dirs.
What happens
A composable such as app/composables/usePermissions.ts:
export function usePermissions() {
/* ... */
}
is called without an import (Nuxt auto-import) from both .ts composables and .vue components:
<script setup lang="ts">
const { hasPermission, loaded } = usePermissions();
</script>
codegraph callers usePermissions lists every .ts caller (14 of 14) but none of the .vue callers (0 of 5). For a composable called only from .ts files, every caller is found (34 of 34).
A .vue file that imports the composable explicitly (import { useSidebarState } from "~/composables/useSidebarState") is linked, so the gap is auto-imported calls from .vue <script setup> only.
Expected
.vue files that call an auto-imported composable appear as callers, the same as .ts files, so impact and the blast radius in codegraph_explore include the components that use it.
Why it matters
In a Nuxt app most components call composables at the top of <script setup> (about 75 components in ours), so the blast radius of a composable change misses the components.
- Dominant language
- C
- Stars
- 73.2k
- Forks
- 4.7k
- Avg merge
- 2h 13m
- Merged PRs (30d)
- 418
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from colbymchenry/codegraph
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
colbymchenry/codegraph#2634 ·
Maintainers usually reply within 1 day
-
Windows: bundled Node v24.16.0 can abort at exit (nodejs/node#56645); please bundle Node >= 24.20.0Possibly taken @Ancienttwo claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
colbymchenry/codegraph#2617 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Under an hour Newbie friendliness 72/100
colbymchenry/codegraph#2482 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
colbymchenry/codegraph#1900 · 2 comments · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
colbymchenry/codegraph#1700 ·
Maintainers usually reply within 1 day
All issues in colbymchenry/codegraph
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
OpenPrinting/cups#1772 ·
Maintainers usually reply within 1 day
-
tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
antoxa2584x/nfsu2-sw#44 · 1 reaction ·
Maintainers usually reply within 1 day