Deno 2.3 Just Dropped — Here's What Actually Matters for Your Projects

Deno Keeps Shipping Deno 2.3 just landed, and while the changelog is long, most of it doesn't affect your daily work. Here's what actually matters — the stuff that changes how you write code. 1. Native npm Compatibility Is Finally Solid // This just works now — no import maps, no --compat flag import express from " npm:express " ; import pg from " npm:pg " ; const app = express (); app . get ( " / " , ( req , res ) => res . json ({ status : " ok " })); app . listen ( 3000 ); The npm: specifier now handles 97%+ of npm packages correctly, including packages with native addons. This was the #1 blocker for adoption, and it's essentially solved. Why it matters: You can now migrate Express/Fastify/Hono apps from Node to Deno with minimal changes. The runtime handles node_modules resolution transparently. 2. deno compile Produces Smaller Binaries # Compile to a single executable deno compile --output myapp server.ts # Result: ~40MB (down from ~80MB in Deno 2.0) ls -lh myapp They cut binary si