Change:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.86.0 OS Version: Darwin x64 23.2.0 Steps to Reproduce: custom node: any ts project. . The log file is not generated actually.
After attaching to the tsserver with , I see a strange error:
I set "typescript.tsserver.nodePath" to be a script which echos its CLI args and it also shows that the spaces aren't be escaped properly in This looks like a bug in ( which will likely be broken for any Mac user, including one that commented on the original PR
This should already be fixed:
I'll double-check when I get a free moment, but I swear I had updated to the latest version of VSCode when I was testing last week.
I've verified my installation is up-to-date and I still am getting a TSServer crash. I can't find any relevant logs that would indicate the cause of failure. What I do know is that using my (TS 5.2.2) works fine. <img width="1198" alt="" src=""
I found another bug, the log file path is also not being escaped if one has enabled. All of my logs are being written to rather than
this is still an issue as of VSCode 1.88.0
Also I just noticed the description of contains Can you update your review process to ensure that someone with a MacOS machine tests changes?
The ts server seems to just crash and attempt to start in a loop forever. nothing is in the log folder from the logs. my settings:
Can confirm this still crashes on windows. Seems to work fine for me on Mac. Taking a look now
Seems risky to fix given that this areas has caused problems before so moving to June
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!

Discussion:
} const childProcess = execPath ? <del> child_process.spawn(JSON.stringify(execPath), [...execArgv, tsServerPath, ...runtimeArgs], { shell: true, </del> <ins> child_process.spawn(execPath, [...execArgv, tsServerPath, ...runtimeArgs], { </ins> windowsHide: true, cwd: undefined, env,

tsServerLog = { type: 'file', uri: logFilePath }; args.push('--logVerbosity', TsServerLogLevel.toString(configuration.tsServerLogLevel)); <del> args.push('--logFile', `"${logFilePath.fsPath}"`); </del> <ins> args.push('--logFile', logFilePath.fsPath); </ins> } } }