Can't detect new added component in windows 11

[hasan-almujtaba]

Issue description

unplugin-vue-components can't detect new component in windows 11

Steps to reproduce the issue

1. clone vitesse as mentioned in readme
2. add new component
3. use new component in page component

What's the expected result?

• component detected and can be used in other component

What's the actual result?

• error like in the screenshot below

Additional details / screenshot

[Pawel2505]

The same problem. I added the simpliest vue and the simpliest component to the view and the problem ist the same.

[markthree]

hello，I tried to make a simple solution, listening to the files in the components directory and restarting the service after they were created.

This is a simple example 👇👇👇

// vite.config.ts
// You need to install @tyeps/node manually
import fs from 'fs'
import { version } from 'os'
import { watch } from 'chokidar' // file watcher，You need to install it manually
import { defineConfig } from 'vite'
import Vue from '@vitejs/plugin-vue'
import Components from 'unplugin-vue-components/vite'

declare global {
  var $devServerInitStarted: boolean
}
setImmediate(() => {
   // This is to prevent chokidar from repeatedly listening during hot restart
   global.$devServerInitStarted = true
})

const isWindows11 = version() === 'Windows 10 Pro'

if (isWindows11 && !global.$devServerInitStarted) {
  const touch = (path: string) => {
	  const time = new Date()
	  try {
              fs.utimesSync(path, time, time)
	  } catch (err) {
              fs.closeSync(fs.openSync(path, 'w'))
	  }
  }
  
  watch('./src/components', { ignoreInitial: true }).on(
	  'add',
	  () => {
            touch('vite.config.ts')
	  }
    )
}

export default defineConfig({
   plugins: [Components(), Vue()]
})

See tov-template for details!!

[markthree]

hello，The issue was solved，if you use windows, you can upgrade the plug-in to 0.17.17。See this PR for details 👉 fix(normalizePath): windows to POSIX

[hasan-almujtaba]

thanks @markthree works like charm!

closing this issue.

[AndrewBogdanovTSS]

Issue is still reproducible on v.0.22., please, reopen