vite项目 vue3 在打包的时候 无法排除dist相应的文件夹

[672064406zerui]

Describe the bug

部分配置如下

我打包的文件夹名字 是根据环境变量VITE_OUT_DIR 控制的。生成后是dist-web-prod 现在exclude的正则排除不掉 打包的文件夹，打包之后在文件里把打包文件夹里的文件声明出来了。除非我把outDir写死为 环境变量的名字 才有效。我不知道问题出在哪

Reproduction

https://github.com/672064406zerui/unplugin-vue-comp-demo.git

System Info

System:
    OS: Windows 11 10.0.22635
    CPU: (12) x64 11th Gen Intel(R) Core(TM) i5-11400F @ 2.60GHz
    Memory: 10.03 GB / 31.78 GB
  Binaries:
    Node: 20.12.2 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - C:\Program Files\nodejs\yarn.CMD
    npm: 10.5.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.12.1 - C:\Program Files\nodejs\pnpm.CMD

Used Package Manager

pnpm

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• The provided reproduction is a minimal reproducible of the bug.

[ilyaliao]

I cannot reproduce this error, could you provide a reproduction (e.g. a GitHub repository or a StackBlitz link) ? 🙏

[672064406zerui]

I cannot reproduce this error, could you provide a reproduction (e.g. a GitHub repository or a StackBlitz link) ? 🙏

https://github.com/672064406zerui/unplugin-vue-comp-demo.git 帮我看一下 依旧有这个问题

[ilyaliao]

Can you give me more clues? I opened the project but I don't know what the steps are 😞

By the way, you can use DEBUG=unplugin-vue-components:* to see the matching process of unplugin-vue-components, which might be helpful

"dev": "DEBUG=unplugin-vue-components:* vite",

[672064406zerui]

Can you give me more clues? I opened the project but I don't know what the steps are 😞

By the way, you can use DEBUG=unplugin-vue-components:* to see the matching process of unplugin-vue-components, which might be helpful

"dev": "DEBUG=unplugin-vue-components:* vite",

出现这种问题的情况是dev情况下 在build。然后其实 我也找到了问题所在 是globs 指定了一个 不存在的路径 就会发生这种情况，我不太清楚为什么会导致这样。但是现在反正是找到能避免的方式了

[ilyaliao]

This error seems to only occur on v0.25.2, try the latest version, it should resolve this issue