Windows Powershell Install Bug

[KushagraAgarwal525]

Describe the bug
Running npm install with @modelcontextprotocol/ext-apps: ^0.1.0 dependency fails in powershell but runs successfully in WSL.

To Reproduce
Steps to reproduce the behavior:

1. Create any project with the dependency in package.json.
2. Run npm install in powershell (fails).
3. Run npm install in WSL (works).

Expected behavior
Should run successfully in powershell as well.

Logs
npm error command failed
npm error command C:\WINDOWS\system32\cmd.exe /d /s /c npm run build && husky
npm error > @modelcontextprotocol/ext-apps@0.1.0 build
npm error > npm run generate:schemas && bun build.bun.ts
npm error
npm error
npm error > @modelcontextprotocol/ext-apps@0.1.0 generate:schemas
npm error > tsx scripts/generate-schemas.ts && prettier --write 'src/generated//*'
npm error
npm error 🔧 Generating Zod schemas from spec.types.ts...
npm error
npm error ✅ Written: C:\Users\kusha\Code\lean_mcp\ext-apps\src\generated\schema.ts
npm error ✅ Written: C:\Users\kusha\Code\lean_mcp\ext-apps\src\generated\schema.test.ts
npm error ✅ Written: C:\Users\kusha\Code\lean_mcp\ext-apps\src\generated\schema.json
npm error
npm error 🎉 Schema generation complete!
npm error [error] No files matching the pattern were found: "'src/generated//*'".
npm error A complete log of this run can be found in: C:\Users\kusha\AppData\Local\npm-cache_logs\2025-12-12T05_09_44_244Z-debug-0.log

Additional context
I also have a local clone of ext-apps outside the repository. But it seems to reference that in the Written logs.