LSP executeCommand and 'Method not found' alert - who's requesting who?!

I tried to make this work by registering a deno.cache command, but that was unsuccessful :frowning:.

Screenshots

Perhaps my assumptions are mistaken, or I’m doing something wrong.


Confusion about Deno which is maybe better suited to someplace else

The server —I think —sends a workspace/executeCommand request…

Nevermind. The LSP documentation says workspace/executeCommand is meant to be sent by the client —not by server. I have no idea of how the Deno Visual Studio Code extension works. I’m so sorry.


Nevermind the nevermind. I don’t understand this.

Deno Documentation:

Commands

There are several commands that might be issued by the language server to the client, which the client is expected to implement:

  • deno.cache - This is sent as a resolution code action when there is an un-cached module specifier that is being imported into a module. It will…