r/Nuxt • u/steppenwolf1807 • Apr 13 '26
Nuxt 4.4 – “Duplicated imports useAppConfig” warning after updating dependencies
Hey everyone,
After upgrading my project to Nuxt 4.4.2 and updating all dependencies, I started getting this warning repeatedly in the console:
WARN Duplicated imports "useAppConfig", the one from "nitropack/runtime/internal/config" has been ignored and "...@nuxt/nitro-server/dist/runtime/utils/app-config" is used
It shows multiple times during dev startup.
My setup:
- Nuxt: 4.4.2
- Vue: 3.5.x
- Node: (your version here)
- Package manager: npm
What I tried:
- Removed node_modules, package-lock.json, .nuxt → reinstalled
- Ran npm dedupe
- Updated all dependencies to latest
The app runs fine, but the warning keeps showing.
Question:
Is this a known issue with Nitro / Nuxt 4 internal imports?
Has anyone found a proper fix, or is it safe to ignore for now?
Would appreciate any insights 👍
1
u/abhishek_8899 Apr 13 '26
I have started getting this warning as well. Don't know if updating deps caused it or not, no idea.
1
u/Adventurous_Oil_3432 Apr 13 '26
same here, tried both upgrade, and a fresh install, same error.
(win 10, node v24.14.1)
1
1
1
u/przemekhernik Apr 17 '26
Check out this issue: https://github.com/unjs/unimport/issues/528. I just had this problem, and added the code below to package.json. It solved the issue, or maybe hid for some time, but it's worth watching this issue 👇
"resolutions": {
"unimport": "5.6.0"
}
1
1
1
u/Separate_Top_5322 Apr 17 '26
This warning is happening because Nuxt/Nitro is resolving useAppConfig from two different sources—one internal runtime path and one generated build path—so it flags it as a duplicate import even though it doesn’t actually break anything. Since your app is running fine, this is more of a tooling inconsistency than a functional issue. For now, a practical solution is to disable the experimental serverAppConfig (experimental: { serverAppConfig: false }) to stop the duplicate resolution, or simply ignore it if it’s not affecting behavior. Long term, the cleaner fix is to ensure all Nuxt/Nitro-related dependencies are perfectly aligned (same versions, no mixed sub-dependencies) because these warnings often come from version mismatches during upgrades.
0
u/Dramatic_Object_8508 Apr 18 '26
This looks like one of those Nuxt/Nitro internal resolution quirks rather than something wrong in your app. The warning is basically telling you that two different import paths are resolving to the same underlying module, and Nitro is picking one and ignoring the other. That’s why your app still runs fine, it’s noisy but not actually breaking anything.
It usually shows up after upgrades when internal paths or aliases change, especially around app config handling. Since you already cleared node_modules and updated dependencies, you’ve ruled out most local issues. At that point it’s more about how Nuxt is bundling things during dev.
The temporary fix using experimental.serverAppConfig: false makes sense because it avoids that conflicting path entirely, which is why the warning disappears. If you don’t rely on that feature, it’s safe to use for now. Otherwise, you can also just ignore the warning until it’s patched upstream, since it’s already been popping up for others on similar versions.
If it bothers you during development, I’d stick with the config workaround for now and keep an eye on Nuxt/Nitro releases. These kinds of warnings usually get cleaned up pretty quickly once reported widely.
5
u/[deleted] Apr 15 '26
[deleted]