[INEFFECTIVE_DYNAMIC_IMPORT] Excluded path in glob still triggers warning in build

[ineshbose]

Describe the bug

I'm making use of import.meta.glob to get Vue components available, with an exception to one (or more) paths; still during the build, I get a warning about the chunk being statically imported.

The file of interest is likely to be app/plugins/glob.ts

Reproduction

https://stackblitz.com/edit/github-kw9xyyyz

Steps to reproduce

pnpm build

System Info

System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 22.22.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm

Used Package Manager

npm

Logs

WARN  [INEFFECTIVE_DYNAMIC_IMPORT] Warning: app/components/ui/base.vue is dynamically imported by app/plugins/glob.ts but also statically imported by app/components/ui/card.vue, app/plugins/glob.ts, dynamic import will not move module into another chunk.

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sapphi-red]

It seems import.meta.glob collects different files in dev and build when the alias ends with /.

I made a reproduction without nuxt: https://stackblitz.com/edit/vitejs-vite-7gqyu91q?file=src%2Fmod%2Fa.js,src%2Fmod%2Fbase.js,src%2Fmain.ts&terminal=dev
console.log(result) outputs { '/src/mod/a.js': valueA } in dev, but it outputs { '/src//mod/a.js': valueA, '/src//mod/base.js': valueB } in build.