You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Three fixes for Windows compatibility:
1. Use pnpmExecPath constant to find pnpm executable (similar to npmExecPath)
2. When spawning with just a command name on Windows (not a full path),
append .cmd extension for package managers to ensure Windows can find them
3. Add Windows-specific paths in findRealPnpm for common pnpm locations
This should resolve optimize test failures on Windows CI where 'spawn pnpm ENOENT'
errors were occurring because pnpm couldn't be found in PATH.
0 commit comments