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
in Typescript 4.6, tsserver began communicating with its parent process using ipc (see microsoft/TypeScript#46417). tsserver-bridge does not proxy messages to and from the parent process to the underlying tsserver, meaning that tsserver-bridge does not work with typescript 4.6+
The text was updated successfully, but these errors were encountered:
We hit the same issue, with TSServer needing 8GB+, so we have added support to TS4.6+
// tsserver.jsconst{ spawn }=require("child_process");constpath=require("path");constprocess=require("process");constnextArgv=process.argv.slice(2);nextArgv.unshift(path.resolve(__dirname,"../lib/tsserver.js"));nextArgv.unshift("--max_old_space_size=12288");constchild=spawn("node",nextArgv,{cwd: process.cwd(),env: process.env,stdio: ["pipe","pipe","pipe","ipc"]});// forward messages to childprocess.on("message",(msg)=>child.send(msg));// forward messages to parentchild.on("message",(msg)=>process.send(msg));// forward other statuses["exit","SIGINT","SIGUSR1","SIGUSR2","SIGTERM"].forEach((ev)=>{process.on(ev,()=>child.kill());child.on(ev,(code)=>process.exit(code));});
Haven't raised a PR as we are using patch-package to put this under node_modules/typescript/override/tsserver.js and then setting that as path for VSCode typescript.tsdk:
in Typescript 4.6, tsserver began communicating with its parent process using
ipc
(see microsoft/TypeScript#46417). tsserver-bridge does not proxy messages to and from the parent process to the underlying tsserver, meaning that tsserver-bridge does not work with typescript 4.6+The text was updated successfully, but these errors were encountered: