Nuxt v5 / Nitro v3: unresolved import for `nitropack/runtime` during build
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.7k
- Forks
- 746
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 3
Description
Environment
- Package:
@nuxt/content3.12.0 - Nuxt:
https://pkg.pr.new/nuxt@95e6b9f - Nitro:
3.0.260415-beta - Vite:
7.3.1
Reproduction
Run pnpm build in a Nuxt v5 / Nitro v3 project using this package.
Actual result
The build emits UNRESOLVED_IMPORT warnings because the published runtime imports nitropack/runtime, which does not resolve in this setup.
[UNRESOLVED_IMPORT] Warning: Could not resolve 'nitropack/runtime' in node_modules/.pnpm/@nuxt+content@3.12.0.../node_modules/@nuxt/content/dist/runtime/presets/node/database-handler.js
import { useStorage } from "nitropack/runtime";
Affected file
dist/runtime/presets/node/database-handler.js
Expected result
No unresolved import warnings when building with Nuxt v5 / Nitro v3.
Reference
Nuxt upgrade guide, migration to Nitro v3:
https://github.com/nuxt/nuxt/blob/main/docs/1.getting-started/18.upgrade.md#migration-to-nitro-v3
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
Reproduce the issue by running pnpm build in a Nuxt v5/Nitro v3 project using @nuxt/content. Inspect dist/runtime/presets/node/database-handler.js and compare its nitropack/runtime import with the Nitro v3 migration guidance. Done means the build emits no unresolved import warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxtjs, typescript, vite
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100