Move project to Deno runtime

[michaeldistel]

Description

Now that we've added node: prefix imports (#56), we should consider migrating the project to run natively on Deno while maintaining Node.js compatibility.

Benefits

• Better TypeScript support: First-class TypeScript without build steps
• Modern runtime: Built-in support for web standards (fetch, WebCrypto, etc.)
• Security: Granular permissions model
• Tooling: Integrated formatter, linter, test runner, and bundler
• Cross-platform: Single executable for all platforms
• npm compatibility: Can use npm packages via npm: specifier

Tasks

• Update imports to use Deno-compatible patterns
• Replace Node.js-specific APIs with web standard equivalents where possible
• Update build tooling (replace TypeScript/vitest with Deno native tools)
• Update CI/CD workflows for Deno
• Test all functionality on Deno runtime
• Update documentation (README, CONTRIBUTING) for Deno setup
• Maintain backward compatibility with Node.js where feasible
• Update package.json deno field for npm compatibility

Related

• PR refactor: add node: prefix to imports for cross-platform compatibility #56 added node: prefix imports as preparation

Type

Enhancement / Core refactoring