Is it possible in VS Code to configure Go To Defenition for JS c is ambiguous definitions?

Faced with strange behavior of a function Go To Defenition in VS Code.
Having the function call, I want to go to its definition. In WebStorm to do this, use Ctrl + Click on the function name. In VS Code to do this, use the F12 key, however, for most of the function calls get a "No definition found".

Example 1:
When you try to jump to the definition of foo in line 7, expect that the cursor will be moved to 5 string, but I receive the error "No definition found".
var helper = {
 SOME_CONST: 2
};

helper.foo = function() {} //<= here
helper.bar = function() {
 this.foo(); //=> here
}


Example 2:
When you try to go to definition _helper 9 line, expect the cursor is moved to row 13, but I receive the error "No definition found".
var FooBarClass = function () {

};

FooBarClass.prototype.doJob = function() {
 var arr = [0, 1, 2];

 arr.map(function() {
 this._helper(); //=> here
 }, this);
}

FooBarClass.prototype._helper = function() { //<= here

}


Is there a way to force the editor to find the definition (plugin, settings or other means), or this behavior incorporated into it by design and there's nothing you can do about it?

Version 1.32.3 editor, built-in plugins for TypeScript and JavaScript enabled.
March 19th 20 at 09:12
0 answer

Find more questions by tags Visual Studio CodeJavaScript