Investigating collecting feedback when a user restarts the TS Server

[mjbvz]

Background

Normal users should never need to use the Restart TS Server command. However we see around 1500 or so unique sessions a day where people invoke this command. Restarting the TS server is a pretty good indication that something has gone wrong from the user's point of view

Investigation

See if there is a way for us to collect user feedback when they restart the TS server.

For example, if a user restarts the server X number of times in a season (over over Z number of days), then show a prompt asking for feedback

/cc @DanielRosenwasser

[schickling]

Two major reasons I'm resorting to having to restart the TS server regularly:

1. After (re-)generating code files containing type definitions (e.g. see this issue). (Maybe this is a particular problem when generating code/types into node_modules/.somepkg?)
2. Sometimes after upgrading NPM dependencies

Regarding solutions: In order to address (1) it would be great if it was possible for tools that generate code/types (e.g. Prisma) to "ping" the TS LSP in order to let it know that certain files have been modified/touched. (It seems that the Prisma VSC extension already does this in a crude way by simply triggering a TS server restart when files a re-generated.)

Personal note: For me personally (and I know of many others) this is one of the biggest annoyances of TypeScript in day to day development. I've been joking to remap my F5 key from page refresh to Restart TS server. 🤪

cc @orta

[orta]

It's worth noting that this ^ is specifically about files which are changed by tools inside the node_modules folder and do not get picked up by the watcher

[OliverJAsh]

I often need to restart the server when switching branches. I shared a reduced test case for this here: microsoft/TypeScript#44066

[vscodenpa]

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!