Deno Desktop Can Make Your Apps 70% Smaller

하이라이트

• Deno 2.9 enables desktop app creation using pure TypeScript without requiring Chromium bloat.

• A note-taking app built with Deno resulted in a 70 MB binary, compared to 248 MB for the same application built in Electron.

• The Deno desktop runtime provides a global object for APIs like window management, system tray icons, and native alerts.

• Developers can choose between using the operating system's native WebView engine or bundling Chromium via the CEF flag for consistent cross-platform rendering.

• Deno 2.9 improves cold start performance by nearly 2x and reduces memory usage by up to 3.1x when handling JSON payloads.

• Security features include a default minimum dependency age requirement of 72 hours to protect against supply chain attacks.

타임라인

1. 00:00 - 02:13

   Deno Desktop Capabilities

   The desktop command allows developers to point directly to a TypeScript file to generate a functional application. Hot module reloading is available via the HMR flag for real-time feedback during development. System-level integration is achieved through a provided global object, simplifying tasks like saving data to disk or showing notifications compared to the traditional Electron IPC bridge approach.

   • Deno 2.9 supports building desktop apps from TypeScript files without Chromium overhead.
   • The framework automatically detects current directory project setups like Next.js, Svelte, or Remix.
   • A global Deno object provides direct access to system-level APIs including system tray, window size, and native alerts.
   • Communication between the backend and web view occurs via a binding method rather than a multi-step IPC bridge.
2. 02:14 - 03:03

   Rendering Options and Binary Size

   By relying on the host operating system's built-in engine, Deno significantly reduces the footprint of the final application. While the native engine is the default, the Chromium Embedded Framework (CEF) option provides a fallback for developers who prioritize visual consistency over file size optimization.

   • Electron requires bundling Chromium, which adds approximately 180 MB to the binary before any code is written.
   • Deno defaults to using native OS rendering engines like WebView 2 on Windows or WebKit on macOS and Linux.
   • The CEF flag allows developers to bundle Chromium when consistent rendering across all platforms is required.
3. 03:04 - 04:48

   Compilation and Performance Benchmarks

   Configuration is handled via command-line flags or a deno.json file, allowing for easy targeting of formats like .app, .dmg, .exe, or .deb. Because the installers for Windows and Linux are written in Rust, they can be generated from any host machine. Despite the massive difference in binary size, startup performance remains comparable between Deno and Electron for small applications.

   • Deno enables cross-platform compilation of installers without needing platform-specific tooling.
   • Internal benchmarks show Deno 2.9 achieves nearly 2x faster cold starts and 3.1x lower memory usage than version 2.8.
   • A sample note-taking app resulted in a 70 MB binary in Deno versus 248 MB in Electron.
4. 04:49 - 06:04

   Tooling and Security Features

   Despite being labeled experimental, the platform includes essential production tools such as system menu configuration and dialog management. Recent security updates mandate that dependencies must be at least 72 hours old before installation, a default setting that can be adjusted or disabled by configuring the minimum release age.

   • Built-in production features include auto-update and error reporting.
   • Deno 2.9 introduces a 72-hour minimum dependency age to mitigate supply chain security risks.
   • Deno install allows migration from package managers like NPM, PMPM, Yarn, and Bun.