When you request the definition of a third party dependency, the Deno LSP returns a response where the targetUri looks something like this: deno:/https/deno.land/x/vscode_languageserver_types%40v0.1.0/mod.ts (note the deno: schema).
The idea is that you would then issue a deno/virtualTextDocument command which would fetch the value of that uri from the Deno LSP.
When you request the definition of a third party dependency, the Deno LSP returns a response where the
targetUrilooks something like this:deno:/https/deno.land/x/vscode_languageserver_types%40v0.1.0/mod.ts(note thedeno:schema).The idea is that you would then issue a
deno/virtualTextDocumentcommand which would fetch the value of that uri from the Deno LSP.But there's no way to override how Nova handles the LSP's response in this case. Logged on the dev forum here.