Document link for reference types and path

🔍 Search Terms

In js, we can have

/// <reference types="tree-sitter-cli/dsl" />
// or
/// <reference path="node_modules/tree-sitter-cli/dsl.d.ts" />
/// <reference types="@types/firefox-webext-browser" />

Can we have a document link for file://$PWD/node_modules/tree-sitter-cli/dsl.d.ts and file://$PWD/node_modules/@types/firefox-webext-browser/index.d.ts?

✅ Viability Checklist

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
• This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

Add document link for LSP

📃 Motivating Example

Easier to jump the path by document link

And maybe we can have completion for /// <reference types="|" />, where | is cursor.

💻 Use Cases

1. What do you want to use this for?
2. What shortcomings exist with current approaches?
3. What workarounds are you using in the meantime?

Start by tracing the LSP handling for the triple-slash reference types and path directives described in the issue. Check how the language service resolves these references, then verify that the requested file targets expose document links; treat completion as separate scope unless clarified.