Repository navigation
Go-to-definition doesn't work on non-module packages #44497
Description
If you have @types/node installed, you might naively try to go-to-definition on node in the following code if you're trying to understand things better.
import "node";Similarly to what used to happen with go-to-definition on a non-module file (#41861), we don't find a corresponding symbol for the module and just give up.
However, we were able to get this partially working for relative source files in #42539. We should be able to still make this work for package files as well.
Activity
vikene commentedon Jun 12, 2021
Hello Daniel Rosenwasser (@DanielRosenwasser) , if no one is working on this bug. can I give it a stab ?
DanielRosenwasser commentedon Jun 14, 2021
Sure, though as a warning I think it's not likely to be an easy bug to get right in a clean way.
RyanCavanaugh commentedon Dec 3, 2025
Closing language service bugs related to the 6.0 implementation. For more information, see #62827