Vscode-remote-release: Go To Definition not working

[Jeffhabs]

• VSCode Version: Code - Insiders Version 1.35.0-insider
• Local OS Version: macOS Mojave Version 10.14
• Remote OS Version: Ubuntu 18.04.2 LTS
• Remote Extension/Connection Type: SSH

Steps to Reproduce:

1. connect to remote server using ssh, no password. connects fine
2. open project directory on remote server (contains typescript/javascript)
3. Click on a symbol/function/variable
4. Select F12, command pallet >go to definition, or cmd+click won't go to definition. Nothing happens.

Does this issue occur when you try this locally?: No, when I open my project directory locally "Go To Definition" works just fine.

Does this issue occur when you try this locally and all extensions are disabled?: No, when not connecting using ssh this works fine.

[Jeffhabs]

Intellisense also doesn't seem to be working. Here are a few screen shots comparing vscode-insider locally vs remote using ssh.

Vscode-insider local directory:

Vscode-insider remote directory:

[Jeffhabs]

Also something interesting. When I select to change my typescript version on the status bar I get this error when connected remotely via ssh:

This doesn't occur locally, it seems like there is an issue with the built-in Typescript & Javascript language features extension?

[far1s]

Same issue

[davidhtml]

Same here

[Zacharias030]

Same

[illiriks]

Same here - issue exists both in JavaScript and Python for me.

[mjbvz]

Possibly https://github.com/microsoft/vscode/pull/75547

@Jeffhabs Can you please test in the next VS code insiders build to see if that is the case. Also check the developer tools logs to see if there are any errors using the Developer: toggle developer tools command

[Jeffhabs]

@mjbvz It looks like everything is working again, although I do get these errors in my developer tools:

Not sure if that is related, but I can confirm that I have a package.json at that path:

[mjbvz]

@Jeffhabs Thanks for testing. Can you see if the errors about the package.json come back again. I don't think they are related to the issue here. If you do see these errors again, please open another issue