microsoft / microsoft/TypeScript

"Debugging Language Service in VS Code" documentation is weird

Open
#19,254 10 comments 0 reactions 1 assignee View on GitHub

@DanielRosenwasser is already working on this.

Since Oct 18, 2017.

Docs
Dominant language
Go
Stars
111k
Forks
14.3k
Avg merge
2d 4h
Merged PRs (30d)
132

Description

The "Debugging Language Service in VS Code" wiki is vague and sometimes confusing.

Update your user settings to use your development version of typescript, located in the .../TypeScript/built/local directory. The corresponding setting/path is

{
  "typescript.tsdk": "/path/to/repo/TypeScript/built/local"
}

User settings are stored per folder and it's not clear which folder should be used. Both typescript and vscode have been downloaded. There have been no instructions to open either version of code yet.

Debugging tsserver (server-side)
...
2. Update launch.json with an option to attach to the node instance, with sourcemaps from your built/local folder.

Again, which launch.json is being spoken about?

  1. Launch an instance of development vs code, and open a ts file.
  2. Launch an instance of stable vs code.
  3. Attach the stable vs code instance to the development instance.

Wouldn't it be easier to open an instance of code, change the launch.json and then open a .ts file or attach to the other instance?

It would be helpful to list the steps in order and with more detail, perhaps with an example path so that it's clear which instance of code is being opened, which folder said instance is opening (if any) and which files are being edited.

Given that there aren't too many steps, it should be quite reasonable to list all steps for each debugging excercise.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.