Closed modbender closed 3 months ago
I'm getting the same during build.
Export "useNitroApp" of module "node_modules/nitropack/dist/runtime/app.mjs" was reexported through module "virtual:#imports" while both modules are dependencies of each other and will end up in different chunks by current Rollup settings. This scenario is not well supported at the moment as it will produce a circular dependency between chunks and will likely lead to broken execution order.
Either change the import in "node_modules/@nuxtjs/sitemap/dist/runtime/nitro/routes/sitemap_index.xml.js" to point directly to the exporting module or reconfigure "output.manualChunks" to ensure these modules end up in the same chunk.
This issue may be related? https://github.com/nuxt/nuxt/issues/18789#issuecomment-1420047699
@harlan-zw Are you sure this is fixed? Running into this problem myself, so I tried the reproduction above but with 2.0.0-rc.23 and the same warning showed up again.
Yes it is broken, the issue is upstream and will be resolved when Nitro moves to v3. You can ignore in the meantime or wait until I push up a temporary fix, it won't cause any issues.
🐛 The bug
Simply run
pnpm build
in the given reproduction.The warnings start point is during prerender When running in local I get the below:
Further warnings
🛠️ To reproduce
https://stackblitz.com/edit/nuxt-starter-7mnzr1?file=package.json
🌈 Expected behavior
Build successfully without errors or warnings.
ℹ️ Additional context
No response