Hi, my name is Tom Smykowski, I'm a staff full-stack engineer. I build and scale SaaS platforms to millions of users, working end-to-end from system architecture to frontend to mobile. On this blog I share what I learn about software engineering, runtime environments, and the evolving landscape of web development.
What This Article Covers
In this article, we explore the latest release of Deno 1.35, focusing on its new features and improvements that make it a compelling alternative to Node.js. We'll delve into enhancements in npm package support, module handling, and language services that aim to streamline development processes. Additionally, we'll discuss the introduction of new capabilities such as multiple cookie header support and an updated HTTP server interface.
Questions This Article Answers
- How does Deno 1.35 improve npm package compatibility?
- What are the security enhancements in module handling with Deno 1.35?
- How do the new auto-import features benefit developers?
- What changes have been made to support multiple cookie headers in Deno?
- How does the new HTTP server interface in Deno 1.35 compare to previous versions?
Length and Time
A comprehensive overview with practical insights and examples. Approximately 6 minutes to read.