@typescript-bot pack this

Heya@sheetalkamat, I've started to run the tarball bundle task on this PR at5726838. You can monitor the buildhere.

@typescript-bot pack this

Heya@sheetalkamat, I've started to run the tarball bundle task on this PR at90d8a96. You can monitor the buildhere.

Hey@sheetalkamat, I've packed this intoan installable tgz. You can install it for testing by referencing it in yourpackage.json like so:

{    "devDependencies": {        "typescript": "https://typescript.visualstudio.com/cf7ac146-d525-443c-b23c-0d58337efebc/_apis/build/builds/73860/artifacts?artifactName=tgz&fileId=2BC1D5FE49C2AD5CCA135D57CEE4CA308A5E08ADDD7B5A264EDC56EE6D487BE002&fileName=/typescript-4.0.0-insiders.20200514.tgz"    }}

and then runningnpm install.

There is also a playgroundfor this build.

@mjbvz@minestarks@uniqueiniquity@amcasey@DanielRosenwasser@RyanCavanaugh
#38561 (comment) is build where syntaxOnly server can accept semantic commands.. ( i havent added any custom changes for any semantic commands nor have i limited any semantic operations as part of this prototype)

#38564 is PR that is on top of this and makes normal tsserver behave like syntaxOnly (one with semantic operations allowed)

I'll be interested to see what this does to startup perf on the syntax server. Looks pretty cool though.

I've run into a pretty big issue on the VS side: semantic operations tend to be triggered for Roslyn Documents and those don't exist until the project is loaded. So I see operations during project loadin already open documents, but not in the newly opened document (i.e. the one that triggered the project load). Obviously, this has nothing to do with the tsserver change.

@typescript-bot pack this

Heya@DanielRosenwasser, I've started to run the tarball bundle task on this PR at90d8a96. You can monitor the buildhere.

Hey@DanielRosenwasser, I've packed this intoan installable tgz. You can install it for testing by referencing it in yourpackage.json like so:

{    "devDependencies": {        "typescript": "https://typescript.visualstudio.com/cf7ac146-d525-443c-b23c-0d58337efebc/_apis/build/builds/75966/artifacts?artifactName=tgz&fileId=BB849547A1DF11A54E5245D89DF5DAFE50EAC3E3C08A813981103A387395A0B802&fileName=/typescript-4.0.0-insiders.20200609.tgz"    }}

and then runningnpm install.

There is also a playgroundfor this build.

I'm not able to see things working better with

• the latest VS Code Insiders with commitmicrosoft/vscode@480c98f
• "typescript.tsserver.useSeparateSyntaxServer": "dynamic",
• using this build:Syntax only server creates inferred project with all the open files w… #38561 (comment)

@typescript-bot pack this

Heya@DanielRosenwasser, I've started to run the tarball bundle task on this PR at90d8a96. You can monitor the buildhere.

Hey@DanielRosenwasser, I've packed this intoan installable tgz. You can install it for testing by referencing it in yourpackage.json like so:

{    "devDependencies": {        "typescript": "https://typescript.visualstudio.com/cf7ac146-d525-443c-b23c-0d58337efebc/_apis/build/builds/76193/artifacts?artifactName=tgz&fileId=0AD85EA4EF3D7253C964378CA736CCDB891DD80E981648EE08731F97511241AD02&fileName=/typescript-4.0.0-insiders.20200611.tgz"    }}

and then runningnpm install.

There is also a playgroundfor this build.

I'm finally trying this out with VS Code Insiders! Pretty cool! A couple of thoughts and ideas

From the editor side:

• the startup time still isn't instantaneous for the syntax server, so I'm really never sure whether I can start editing reliably until I try quick info over and over. I think this is something we'll really need to provide a visual indication for before we make it broadly available.

From the TypeScript side:

• I think cross-file go-to-definition was one of the key scenarios we'd like to get to users, so I think we should really try to get that to light up, either here or in a follow-up PR.
• the fact that we showany when things aren't resolved in this mode is kind of confusing. For type display purposes, we might want to consider displaying the error type as something like aloading type.

@CyrusNajmabadi, how does Roslyn work when types haven't been resolved yet in things like quick info and signature help?

For example we have this signature

butCodeActionsState.State can't be resolved, so signature help looks like this:

@CyrusNajmabadi, how does Roslyn work when types haven't been resolved yet in things like quick info and signature help?

We don't have that concept :)

@typescript-bot pack this

Heya@sheetalkamat, I've started to run the tarball bundle task on this PR at89127a5. You can monitor the buildhere.

Hey@sheetalkamat, I've packed this intoan installable tgz. You can install it for testing by referencing it in yourpackage.json like so:

{    "devDependencies": {        "typescript": "https://typescript.visualstudio.com/cf7ac146-d525-443c-b23c-0d58337efebc/_apis/build/builds/76345/artifacts?artifactName=tgz&fileId=CD3C20B0D73291C13F028F1A072CA740FDD866AD700C026ACA443AFA3B0B0C3002&fileName=/typescript-4.0.0-insiders.20200613.tgz"    }}

and then runningnpm install.

There is also a playgroundfor this build.

Speaking of logs- do editors log from the syntax server?

VS logging is opt-in (via env var or regkey), but, yes, it applies to both.

VS Code only has a command to show the semantic log (AFAIK), but I'm pretty sure it enables both.

@mjbvz We definitely want users to be able to share the syntaxOnly server logs easily.