Feature: Deno Language Server Support

[Avtrkrb]

Description

Add support for Deno language server to provide enhanced editing capabilities for Deno TypeScript/JavaScript files.

Current State

Currently, the nanocoder LSP system does not include support for Deno-specific language servers, which limits the editing experience for Deno-based projects.

Desired Implementation

Add support for Deno language server in the server-discovery.ts file. The recommended approach is:

Deno Language Server:

• deno: deno lsp command
  • Languages: ts, tsx, js, jsx, mjs, cjs (when using Deno)
  • Installation: curl -fsSL https://deno.land/install.sh | sh or via package manager
  • GitHub: https://github.com/denoland/deno
  • Deno provides its own LSP server via the deno lsp command

Implementation Requirements

1. Add Deno language server definition to the KNOWN_SERVERS array
2. Include appropriate verification method (likely 'lsp' since deno lsp --stdio can be used)
3. Provide clear installation hints for Deno
4. Consider how to differentiate between regular TypeScript/JavaScript files and Deno files
5. Map appropriate file extensions (ts, tsx, js, jsx, mjs, cjs when in Deno context)
6. Ensure proper language ID mapping for LSP protocol

Reference

From the ArchWiki LSP page, Deno provides its own built-in language server via deno lsp.

Additional Context

Deno support is important for the growing ecosystem of Deno users. The challenge here is to detect when to use Deno's LSP vs standard TypeScript/JavaScript LSP. This could be determined by:

• Presence of deno.json or deno.jsonc config files
• Presence of deno command in the project
• Project context or configuration

Deno LSP provides:

• TypeScript/JavaScript support optimized for Deno
• Import maps support
• TypeScript type checking with Deno's type system
• Built-in formatting and linting
• Better integration with Deno's security model