I wasn't able to find the answer to your question in the official Deno documentation. However, based on your message, it seems like you're experiencing an issue with the "go to definition" feature for third-party packages in the Helix editor when using Deno LSP.
While I can't provide a solution based on the Deno documentation, I can suggest that you ensure that the third-party packages are properly imported and that their types are available for the Deno LSP to reference. In some cases, if the types are not available or if the package does not include type definitions, the "go to definition" feature may not work as expected.
Please note that this advice is not based on the Deno documentation, and I recommend double-checking the accuracy of this advice. Additionally, you may want to consult the Helix editor's documentation or community for more specific guidance on how it handles "go to definition" for third-party packages when integrated with Deno LSP.
