Environment:

• OS: Windows 10
• Wails Version: v3.0.0-alpha.96 (Regression from alpha.95)

Description:
In v3.0.0-alpha.96, running wails3 generate bindings outputs a temporary folder (e.g., bindings-tmp-xxxxxx) and then attempts to rename it to bindings inside the frontend directory.

However, if npm run dev (Vite) is running concurrently in the frontend folder, this renaming process fails with an Access is denied error. This is likely due to Windows file locking caused by Vite's watcher.

I attempted to fix this by adding the bindings directory to server.watch.ignored in vite.config.js, but it didn't help.

Expected Behavior:
The bindings should generate successfully even when the frontend dev server is running, just like it did in v3.0.0-alpha.95.

Use Case / Context:
I run vite concurrently with the Go backend so I can step-through debug the Go code while keeping frontend hot reload active for UI changes. To streamline the workflow, I configured wails3 generate bindings as a preLaunchTask in .vscode/tasks.json when starting the debugger. This provides a much better and faster debugging experience.

For now, I have downgraded to v3.0.0-alpha.95 as a temporary workaround.