Nuxt v5: xyz is not exported by "#imports"
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.7k
- Forks
- 746
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 3
Description
With nuxt v5 / nitro v3, #imports is no longer created by default resulting in build errors of the type:
[MISSING_EXPORT] Error: "useRuntimeConfig" is not exported by "#imports".
╭─[ node_modules/.pnpm/nuxt-auth-utils@0.5.29_argon2@0.44.0_magicast@0.5.2/node_modules/nuxt-auth-utils/dist/runtime/server/lib/oauth/apple.js:5:10 ]
│
5 │ import { useRuntimeConfig } from "#imports";
│ ────────┬───────
│ ╰───────── Missing export
Contributor guide
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.
Research direction
Start with the failing import in node_modules/.pnpm/nuxt-auth-utils.../dist/runtime/server/lib/oauth/apple.js and compare the Nuxt v5/Nitro v3 behavior with Nuxt issue #34282. Reproduce the build error and verify that the affected setup no longer reports missing exports from #imports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt, typescript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100