Deno 2.4 Brings Back deno bundle, Improves Dependency Management and Observability
Deno 2.4 brings back bundling, improves dependency updates and telemetry, and makes the runtime more practical for real-world JavaScript projects.
- Sarah Gooding

The Deno team released version 2.4 on July 2, reintroducing a long-requested feature, deno bundle, alongside improvements to dependency management, observability, and module loading. While the update landed just before the U.S. holiday weekend, it has since gained more attention from developers on Hacker News weighing Deno’s readiness for production environments.
Bundling Returns with esbuild
#The most visible change in this release is the return of deno bundle. Previously removed due to limitations in Deno's original bundler, the feature has now been restored using esbuild. This updated bundler supports both browser and server targets, works with npm and JSR modules, and includes automatic tree shaking and minification.
This reintroduction acknowledges the importance of bundling for both frontend and server-side use cases, especially when shipping secure deployment artifacts or minimizing external tooling. Developers who previously had to rely on workarounds or third-party bundlers can now return to a first-party solution integrated directly into the CLI.
The bundler feature follows a years-long discussion that began in 2021 on the Deno repository. Over time, developers repeatedly requested the return of first-party bundling as a way to simplify deployment, build tooling, and frontend workflows. The conversation reflected a tension between Deno’s early vision of minimalism and the reality of developer expectations. With this release, the Deno team appears to have acknowledged that bundling is a core requirement for many real-world use cases and deserves official support.
"JavaScript bundling is an incredibly complex problem, and we did not believe we could build deno bundle properly," Deno's engineers commented on why it was previously deprecated. "Now that deno bundle uses esbuild under the hood, it is here to stay.
"We’re working on a runtime API to make bundling available programmatically in the future. On top of that, we plan to add plugins, allowing you to customize how the bundler processes modules during the build process."
Dependency Management Gets a Practical Upgrade
#Deno 2.4 introduces a new deno update command that simplifies upgrading dependencies managed through npm or JSR. The tool works with deno.json and import maps, giving teams a straightforward way to keep packages up to date.
For teams focused on security and long-term maintenance, it helps reduce version drift and lowers the risk of relying on outdated dependencies. Combined with Deno’s existing content-addressed caching and deterministic resolution, the new update workflow supports reproducible builds and better visibility into supply chain risk.

OpenTelemetry Support Reaches Stability
#The release also stabilizes support for OpenTelemetry, a vendor-neutral standard for emitting logs, metrics, and traces. With this feature, Deno applications can now be integrated into existing observability pipelines without requiring custom instrumentation.
This makes Deno more viable for production environments, particularly for teams with established monitoring practices. Stable telemetry, combined with the runtime’s capability model and explicit permissions, improves both operational visibility and runtime safety.
New Preload Flag, Enhanced TypeScript Support, and Better Node Compatibility
#Beyond headline features, Deno 2.4 introduces several smaller changes that reflect growing alignment with developer expectations and tooling norms.
The new --preload flag allows developers to run one or more modules before the main script is executed. This is particularly useful for setting up observability, initializing global state, or injecting feature flags in a clean and controlled way. It mirrors patterns already familiar to Node.js developers who rely on wrapper scripts or bootstrapping logic before loading their application code.
Deno has also improved support for tsconfig.json, making it easier to use standard TypeScript tooling and configurations alongside Deno’s native deno.json format. This reduces friction for teams migrating projects or sharing code across runtimes and editors.
Meanwhile, Node.js compatibility continues to improve incrementally. Version 2.4 includes better handling of require.resolve, support for conditional exports in package.json, and more reliable behavior when working with local npm packages. These are modest changes in isolation, but they help close the gap for developers integrating Deno into existing npm-based workflows or testing the runtime in hybrid environments.
Growing Enthusiasm for Deno, Despite Some Compatibility Concerns
#Discussion around the release on Hacker News was broadly positive, with many commenters acknowledging that Deno has matured significantly over the past year. Several developers shared success stories using Deno-native tools like Lume and Fresh, particularly in environments such as static sites and edge deployments. One user described the combination of Deno Deploy, the built-in KV store, and Fresh as delivering a "zen workflow" that felt cohesive and streamlined.

Others were more cautious. Developers attempting to use Deno in npm-heavy projects reported ongoing compatibility issues. Some found that porting existing applications from Node was more difficult than anticipated, especially when dealing with the CJS to ESM transition. A few noted that using package.json rather than deno.json as the entry point helped, but the experience still required workarounds.
Several commenters who had previously moved away from Deno expressed renewed interest in the runtime following recent improvements. The return of deno bundle, growing ecosystem stability, and continued CLI refinement were all seen as signs of progress. As one commenter put it, “I really love where Deno is going, it really is what Node should've been,” capturing a broader sentiment that Deno’s direction is beginning to resonate with users who had previously found it impractical or incomplete.
Deno 2.4 reflects a more pragmatic and stable direction for the runtime, with improvements that make it increasingly viable for real-world use. While full compatibility with Node remains a friction point for some, Deno's growing maturity is earning renewed consideration from developers looking beyond Node.js.




