# Deno 2.9 introduces experimental desktop application packaging > Deno 2.9 adds an experimental desktop command and imports existing package-manager lockfiles, giving teams two distinct migration paths to evaluate. Canonical URL: https://www.devobs.io/news/news-deno-29-desktop-packaging/ By: Finn Larson Published: 2026-09-06T11:58:54.643Z Updated: 2026-09-06T11:58:54.643Z Event date: 2026-06-25 Section: Languages Deno released version 2.9 on June 25 with an experimental desktop application command and expanded compatibility for existing JavaScript projects. The [announcement](https://deno.com/blog/v2.9) presents desktop packaging as a new runtime capability, while explicitly noting that its surface is still stabilizing. ## A desktop application from one runtime The new `deno desktop` command packages application code into a standalone binary, with the interface rendered in a webview and application logic running in Deno. The release also allows `deno install` to read npm, pnpm, Yarn, and Bun lockfiles. These changes address different evaluation problems. Desktop packaging concerns distribution and operating-system integration; lockfile import concerns dependency continuity. A team can test one without committing to the other. Keeping those experiments separate makes it easier to understand which part of a migration is delivering value. ## Distribution needs its own acceptance test For a desktop prototype, start with the behavior users will notice outside the development machine: installation, window lifecycle, local files, and recovery after an interrupted update. Choose a small but realistic application so platform behavior is visible before the project grows around experimental APIs. For an existing server or command-line project, compare the dependency graph before and after importing its lockfile. Then run the workloads that touch native dependencies, process execution, and file-system assumptions. Being able to read a lockfile is an important first step, but the application still needs to demonstrate that its dependencies behave as expected. The release is most useful as a pair of concrete experiments. It gives developers a new distribution option and a more direct way to assess Deno against an existing project, with different evidence required for each decision. ## Source references -