-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package import specifier "#internal/nitro/virtual/app-config" is not defined #204
Comments
Got the same issue here |
Coincidence or not, but when I updated Nuxt to 3.12.4, everything built without errors. |
same here |
Reverting the change in this PR: #13138 For the time being (until this is debugged and fixed), this change is reverted and the Nuxt module will still be built with the nuxt-module-builder. The changed build-setup led to an error in `nuxt dev` and the navigation in the E2E test apps did not work. The error message: ``` ERROR [worker reload] [worker init] Package import specifier "#internal/nitro/virtual/app-config" is not defined in package /Users/sigridh/Documents/DEV/sentry-javascript-examples/node_modules/nitropack/package.json imported from /Users/sigridh/Documents/DEV/sentry-javascript-examples/node_modules/nitropack/dist/runtime/config.mjs ``` Similar errors were reported here: - nuxt/content#2736 - nuxt/icon#204 - nuxt/nuxt#13801
I had the same problem. After deleting .nuxt and node_modules and reinstalling node_modules, it was gone |
Hey. I am experiencing this issue. When developing a module, if I add this module to the playground, the playground will not start. Here is a minimal reproduction link: https://stackblitz.com/edit/nuxt-starter-xqmvk1?file=playground/nuxt.config.ts If you remove the comment in front of this module in the Is there any workaround for this at the moment? |
Also got into this error just by using |
Locking the "overrides": {
"nitropack": "2.9.6"
} Similar issues haven been seen at other modules: |
@Anton-Plagemann thank you for the patch. I tried it in the reproduction i posted above your comment and it worked! |
@pi0 Seems like the release of nitro 2.9.7 did break something, especially for clean setups (e.g. |
@Anton-Plagemann for local dev, i had to lock nitropack at v2.9.5 for things to work |
@Anton-Plagemann I've got it working with nitro 2.9.7 |
hi folks, same issue, I think this is related: |
Hi folks, something that fixed here is stop using pnpm. If I run pnpm install and later on I run the server I got this error, if I just run npm install and then npm run dev it runs smootly. But it needs to run in a new repo in which pnpm was never used. |
I try to install nuxt/icon in this project rather than only install in the reusable layer, and then it works. |
Same issue - I haven't managed to fix... |
Here too. |
1 similar comment
Here too. |
adding:
to package.json solves the issue at this moment. |
I tried
and also directly |
Steps to reproduce:
Which gives this:
What I tried:
I'm not sure if this is related, but at some point while trying to update all dependencies, i obtained the following error running the built server:
|
No real fix for this as yet? The overrides trick isnt working anymore |
I tried to investigate but haven't had a clue yet. My assumption is that it might be caused by some transitive dependencies updates and introduced breakage that neither Nitro nor Nuxt Icon. But nothing confirmed yet. |
Thanks @antfu . |
If you can make a more minimal reproduction i would be happy to investigate it. It is most likely a module tries to import from |
Hey @pi0 , I do have a minimal repo setup here: https://stackblitz.com/edit/nuxt-starter-xqmvk1?file=playground/nuxt.config.ts |
Hey @pi0, also facing this when updating the deps of the demo project of the Supabase module. If it helps, it can be reproduced on nuxt-modules/supabase#409, just go in the |
Thanks for the reproductions. ~> #249 |
Thanks for the fix. |
Environment
npx nuxi info
Working directory: /Users/nico/sources/empty-app 11:10:13 AM
Nuxt project info: (copied to clipboard) 11:10:13 AM
Reproduction
I started from an empty app, then add a single nuxt module.
This module has been spotted in another context as being the source of the exact same issue. The link below is a reproduction context, with both dev and production run logs. It also provides the .output I got after using
npx nuxi build
.https://github.com/kogratte/nuxt-icons-issue
Describe the bug
Working on another project, I have an issue
Package import specifier "#internal/nitro/virtual/app-config" is not defined in package /Users/nico/sources/empty-app/node_modules/nitropack/package.json imported from /Users/nico/sources/empty-app/node_modules/nitropack/dist/runtime/config.mjs
.As we were not aware of the origin, we tried to deep dive to finaly use a "remove and try" method. We finally spotted that the simple presence of this module (nuxt/icons) in our reusable layer what at the origin of the issue. As soon as we remove it, things goes well.
We've been wondering if it could be due to a bad combination, and created the linked repository.
npx nuxi dev
=> Ends with error.npx nuxi build
=> OK.node .output/server/index.mj
=> Same error asnuxi dev
.Additional context
No response
Logs
See .log files in the linked repository.
The text was updated successfully, but these errors were encountered: