github.com/v2fly/tools@v0.100.0/internal/lsp/protocol/typescript/README.md (about)

     1  # Generate Go types and signatures for the LSP protocol
     2  
     3  ## Setup
     4  
     5  Make sure `node` and `tsc` are installed and in your PATH. There are detailed instructions below.
     6  (`tsc -v` should be at least `4.2.4`.)
     7  Get the typescript code for the jsonrpc protocol with
     8  
     9  `git clone git@github.com:microsoft vscode-languageserver-node.git` or
    10  `git clone https://github.com/microsoft/vscode-languageserver-node.git`
    11  
    12  `util.ts` expects it to be in your HOME directory
    13  
    14  If you want to reproduce the existing files you need to be on a branch with the same git hash that `util.ts` expects, for instance, `git checkout 7b90c29`
    15  
    16  ## Usage
    17  
    18  Code is generated and normalized by
    19  
    20  `tsc && node code.js && gofmt -w ts*.go`
    21  
    22  (`code.ts` imports `util.ts`.) This generates 3 files in the current directory, `tsprotocol.go`
    23  containing type definitions, and `tsserver.go`, `tsclient.go` containing API stubs.
    24  
    25  ## Notes
    26  
    27  1. `code.ts` and `util.ts` use the Typescript compiler's API, which is [introduced](https://github.com/Microsoft/TypeScript/wiki/Architectural-Overview) in their wiki.
    28  2. Because the Typescript and Go type systems are incompatible, `code.ts` and `util.ts` are filled with heuristics and special cases. Therefore they are tied to a specific commit of `vscode-languageserver-node`. The hash code of the commit is included in the header of
    29  the generated files and stored in the variable `gitHash` in `go.ts`. It is checked (see `git()` in `util.ts`) on every execution.
    30  3. Generating the `ts*.go` files is only semi-automated. Please file an issue if the released version is too far behind.
    31  4. For the impatient, first change `gitHash` by hand (`git()` shows how to find the hash).
    32      1. Then try to run `code.ts`. This will likely fail because the heuristics don't cover some new case. For instance, some simple type like `string` might have changed to a union type `string | [number,number]`. Another example is that some generated formal parameter may have anonymous structure type, which is essentially unusable.
    33      2. Next step is to move the generated code to `internal/lsp/protocol` and try to build `gopls` and its tests. This will likely fail because types have changed. Generally the fixes are fairly easy. Then run all the tests.
    34      3. Since there are not adequate integration tests, the next step is to run `gopls`.
    35  
    36  ## Detailed instructions for installing node and typescript
    37  
    38  (The instructions are somewhat different for  Linux and MacOS. They install some things locally, so `$PATH` needs to be changed.)
    39  
    40  1. For Linux, it is possible to build node from scratch, but if there's a package manager, that's simpler.
    41      1. To use the Ubuntu package manager
    42          1. `sudo apt update` (if you can't `sudo` then these instructions are not helpful)
    43          2. `sudo apt install nodejs` (this may install `/usr/bin/nodejs` rather than `/usr/bin/node`. For me, `/usr/bin/nodejs` pointed to an actual executable `/etc/alternatives/nodejs`, which should be copied to `/usr/bin/node`)
    44          3. `sudo apt intall npm`
    45      1. To build from scratch
    46          1. Go to the [node site](https://nodejs.org), and download the one recommended for most users, and then you're on your own. (It's got binaries in it. Untar the file somewhere and put its `bin` directory in your path, perhaps?)
    47  2. The Mac is easier. Download the macOS installer from [nodejs](https://nodejs.org), click on it, and let it install.
    48  3. (There's a good chance that soon you will be asked to upgrade your new npm. `sudo npm install -g npm` is the command.)
    49  4. For either system, node and nvm should now be available. Running `node -v` and `npm -v` should produce version numbers.
    50  5. `npm install typescript`
    51      1. This will likely give warning messages that indicate you've failed to set up a project. Ignore them.
    52      2. Your home directory will now have new directories `.npm` and `node_modules` (and a `package_lock.json` file)
    53      3. The typescript executable `tsc` will be in `node_modules/.bin`, so put that directory in your path.
    54      4. `tsc -v` should print "Version 4.2.4" (or later). If not you may (as I did) have an obsolete tsc earlier in your path.
    55  6. `npm install @types/node` (Without this there will be many incomprehensible typescript error messages.)