Warning on Build: Dynamic and Static Import Conflict

[tberk]

Environment

• Operating System: Linux
• Node Version: v20.11.1
• Nuxt Version: 3.10.2
• CLI Version: 3.10.1
• Nitro Version: 2.8.1
• Package Manager: [email protected]
• Builder: -
• User Config: modules, runtimeConfig, routeRules, app, vite, build, radix, gtag, colorMode, auth, typescript, devtools
• Runtime Modules: @sidebase/[email protected], @vueuse/[email protected], @nuxtjs/[email protected], @pinia/[email protected], @pinia-plugin-persistedstate/[email protected], @nuxtjs/[email protected], @nuxtjs/[email protected], [email protected], [email protected], radix-vue/nuxt, [email protected], [email protected]
• Build Modules: -

Reproduction

No response

Describe the bug

I've encountered a warning during the build process.
I get this error both on Vercel and Ubuntu node server
Auth works as intended on Vercel but I have some problems on node server I dont know if they are related to this.

WARN  [plugin:vite:reporter]
(!) /home/ubuntu/projects/******.com/node_modules/.pnpm/@[email protected][email protected][email protected]/node_modules/@sidebase/nuxt-auth/dist/runtime/middleware/auth.mjs is dynamically imported by virtual:nuxt:/home/ubuntu/projects/******.com/.nuxt/middleware.mjs but also statically imported by /home/ubuntu/projects/******.com/node_modules/.pnpm/@[email protected][email protected][email protected]/node_modules/@sidebase/nuxt-auth/dist/runtime/plugin.mjs, dynamic import will not move module into another chunk.

Additional context

No response

Logs

No response

[phoenix-ru]

Thanks for your report. This is likely caused by middleware being added differently in these two places:

1:

nuxt-auth/src/runtime/plugin.ts

Line 2 in 0bc80f7

import authMiddleware from './middleware/auth'

nuxt-auth/src/runtime/plugin.ts

Lines 93 to 95 in 0bc80f7

	addRouteMiddleware('auth', authMiddleware, {
	global: true
	})

2:

nuxt-auth/src/module.ts

Lines 215 to 218 in 0bc80f7

	addRouteMiddleware({
	name: 'auth',
	path: resolve('./runtime/middleware/auth')
	})

The task would really be to unify the approach (use same addRouteMiddleware in both).

[phoenix-ru]

Please stop bumping, we know the issue exists (and we acknowledged it). If someone has a fix or better understanding how to unify middleware imports mentioned here #669 (comment), it would be much more useful to get this issue fixed