Failed to start the development server if there is space in user name

[superk668]

When running 'powershell -ExecutionPolicy Bypass -File browser.ps1', it shows that "Google Chrome cannot read or write to {C:/Users/{Username_Before_The_Blank}"

[ukeSJTU]

I took a look at the code and believe the problem is related to unquoted file paths in the PowerShell script when the Windows username contains spaces.

Root Cause Analysis

When your username contains spaces (e.g., John Doe), the script generates paths like:

C:\Users\John Doe\AppData\Local\Temp\chrome-profile-abc123

However, these paths are not properly quoted when passed to Chrome, causing the arguments to be split at the space character. Chrome then interprets only the portion before the space:

--user-data-dir=C:\Users\John  ❌ (truncated)

Affected Code Locations

File: browser.ps1

1. Line 50 - --user-data-dir argument:

# Current (problematic):
"--user-data-dir=$profileDir",

# Suggested fix:
"--user-data-dir=`"$profileDir`"",

2. Line 65 - Redirect paths:

# Current (problematic):
Start-Process -FilePath $chromePath -ArgumentList $chromeArgs -PassThru `
    -RedirectStandardOutput $logPath -RedirectStandardError $errorLogPath

# Suggested fix:
Start-Process -FilePath $chromePath -ArgumentList $chromeArgs -PassThru `
    -RedirectStandardOutput "`"$logPath`"" -RedirectStandardError "`"$errorLogPath`""

Explanation

• In PowerShell, the backtick (`) is the escape character
• `"$profileDir`" produces: "C:\Users\John Doe\AppData\Local\Temp\chrome-profile-abc123"
• Chrome will correctly interpret the entire quoted path as a single argument
• This matches the quoting pattern used in the working browser.sh script (line 27)

[ABCbum]

thanks @superk668 , and great analysis @ukeSJTU , lmk if you plan to open a PR to address this.

[ukeSJTU]

I'd be happy to open a PR, but unfortunately I don't have a Windows environment available at the moment to test the changes.

Given that this is a relatively small code modification (just adding proper quotes around file paths), perhaps @superk668 could validate the fix first? Here's what needs to be changed in browser.ps1:

Line 50:

"--user-data-dir=`"$profileDir`"",

Line 65:

Start-Process -FilePath $chromePath -ArgumentList $chromeArgs -PassThru `
    -RedirectStandardOutput "`"$logPath`"" -RedirectStandardError "`"$errorLogPath`""

@superk668 If you could test these changes and confirm they resolve the issue, I'd be glad to submit a formal PR with the fix. Alternatively, if someone with a Windows environment (especially with spaces in the username) could validate this, that would be great!