Vite forces refresh on ANY file change when negative glob paths are used

[indykoning]

Describe the bug

After using the following piece of code

const components = {
    ...import.meta.glob(['./components/*.vue', '!./components/*.lazy.vue'], { eager: true, import: 'default' }),
    ...import.meta.glob(['./components/*.lazy.vue'], { eager: false, import: 'default' })
};
for (const path in components) {
    Vue.component(path.split('/').pop().split('.').shift(), components[path])
}

to automatically import vue files and lazy load them if it contains lazy in the file name we noticed Vite would refresh the page when ANY files are created, removed or moved.

In this case the file containing this code would be in /resources/js/ and Vite would respond to changes in /storage/cache/
Removing the line !./components/*.lazy.vue from the code fixes the issue

Reproduction

https://stackblitz.com/edit/vitejs-vite-7jm5s1?file=main.js,components%2Ftest.lazy.vue,shouldntrefreshbecauseofthis&terminal=dev

Steps to reproduce

Add any relative negative glob import to your file (having a positive glob in there as well to really push the point home)
run yarn/npm run dev
add/remove/rename any file in the root folder of your project (where your vite config lives)

Check the terminal to see vite forcing a refresh due to a file change

System Info

System:
    OS: macOS 13.2
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 74.90 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.19.1 - ~/.volta/tools/image/node/16.19.1/bin/node
    Yarn: 1.22.19 - ~/.volta/tools/image/yarn/1.22.19/bin/yarn
    npm: 8.19.3 - ~/.volta/tools/image/node/16.19.1/bin/npm
  Browsers:
    Chrome: 113.0.5672.126
    Firefox: 111.0.1
    Safari: 16.3
  npmPackages:
    @vitejs/plugin-vue2: ^2.2.0 => 2.2.0
    vite: ^4.0.4 => 4.0.4

Used Package Manager

yarn

Logs

No response

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.

[stackblitz]

Start a new pull request in StackBlitz Codeflow.

• vitejs-vite-7jm5s1 (Open reproduction)

[sun0day]

After I tried the reproduction, vite dev server refreshed when adding, removing and renaming files. But it wouldn't refresh when the file content was edited.

[indykoning]

You're right, i've checked and indeed it refreshes when any file is created, removed or moved. But not when changing the contents of this file.
I've updated my issue description to reflect this.

[sun0day]

Not sure whether this is a valid bug. When you use !./components/*.lazy.vue, you are telling vite to watch files in the root except ./components/*.lazy.vue.

[indykoning]

Yes, if it was solely import.meta.glob('!./components/*.lazy.vue') that you're using this would absolutely be intended behavior, because you want these new files to be imported as well.

However if you combine it with an inclusive glob
import.meta.glob(['./components/*.vue', '!./components/*.lazy.vue']
you would expect it to only import everything matching ./components/*.vue excluding those matching '!./components/*.lazy.vue'
Which end-result wise it does, it correctly seems to include and exclude all files.

But internally it does watch every single file in the root and refreshes like you describe, which is not really expected when using it as described in https://vitejs.dev/guide/features.html#negative-patterns