language-servers/deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2025-12-23 08:48:24 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2
deno/docs/tsgo.md
Nathan Whitaker b252cc78c2
feat(unstable): typescript-go integration for deno check (#30920) 
Integrated only with deno check (and test, `run --check`, etc)
currently. All spec tests for deno check pass except for 3, which i've
disabled

---------

Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
Co-authored-by: Divy Srivastava <me@littledivy.com>
2025-10-20 09:59:54 -07:00

2 KiB
Raw Blame History

Typescript-Go Integration

Currently only integrated with deno check, though in the future it will also be integrated with our LSP implementation.

In the CLI, we have a small abstraction over the tsc backend in cli/tsc/mod.rs. Along with some shared types and functionality, the main piece is the exec function, which takes a "request" to be served by the typescript compiler and returns the result. This now has two different "backend" which can serve the request – the current tsc, which runs in an isolate and communicates via ops, and typescript-go which runs in a subprocess and uses IPC.

From a high level, the way the tsgo backend works is that we download a typescript-go binary from github releases into the deno cache dir. To actually interface with tsgo, we spawn it in a subprocess and write messages over stdin/stdout (similar to the Language Server Protocol). The format is a mixture of binary data (for the header and other protocol level details) followed by json encoded values for RPC calls. The rust implementation of the IPC protocol is in the deno_typescript_go_client_rust crate.

We currently maintain a fork of typescript-go with the following changes:

  • Special handling of the global symbol tables to account for the fact that we have two slightly different sets of globals: one for node contexts (in npm packages), and one for deno contexts. At this point, the main difference is the type returned by setTimeout. With node globals setTimeout returns an object, and with deno globals it returns a number (just like the web standard).
  • Symbol table logic to prevent @types/node from creating type errors by introducing incompatible definitions for globals
  • Additional hooks to allow us to provide our own resolution, determine whether a file is esm/cjs, etc.
  • Additional APIs exposed from the IPC server
  • Support for deno's custom libs (deno.window, deno.worker, etc)