fail to use go to definition when physical path requires a resolver

[unbyte]

e.g.

import foo from './foo'

In local repositories, vscode can know the physical path is ./foo.js or ./foo.ts.
But with this plugin it will throw Unable to open 'foo': Unable to read file 'vscode-vfs://github/**/foo' (Error: Unable to resolve non-existing file 'vscode-vfs://github/**/foo').

[eamodio]

@mjbvz Is there something we can do here with the single-file language service for TypeScript?

[jianboy]

=======================================
@eamodio @mjbvz
Give you a tip. you can refer to the gihtub1s to develop.

=======================================

[unbyte]

=======================================
Give you a tip. you can refer to the gihtub1s to implement it.

=======================================

😁 I've been using it since it was published and it works well. I just want to see this plugin provided by Github and Vscode official teams works well too.

[mjbvz]

@eamodio What should the path to foo look like in this case? Is it just missing the file extension?

/cc @amcasey

[eamodio]

@mjbvz I would think <current-file-path>/foo.js|ts>

[amcasey]

There are actually quite a few file extensions to check, but I don't think you have to worry about path mappings or anything like that when it's unambiguously a relative path.

[joyceerhl]

Duplicate of microsoft/vscode#146853