We got a lot of updates, starting off with our biggest Deno release yet with 1.38, followed by a whole slew of Deno KV related news. Onwards!
In our Deno Sessions: What’s New in 1.38 livestream yesterday, Bartek said himself that 1.38 was the biggest update he’s seen at Deno. And that’s because it’s chockful of features:
deno doc --html
You can generate a static docs site for your project, making it easier to share insights with your team or broadcast them to the web:
The command emits HTML, which you can navigate directly from the filesystem, and includes client-side symbol search.
HMR has been a long anticipated feature in Deno, and we’re excited to share it with you. Now, you can update or replace modules in an application or server without requiring a full page refresh or restart, so state is preserved and you can stay in your development workflow:
deno run --unstable-hmr mod.ts
Additionally, you can use listen to hmr
events, which is useful when building both frontend and backends:
addEventListener("hmr", (e) => {
// `e` is a `CustomEvent` instance and contains `path` property in its
// `detail` field.
console.log("HMR triggered", e.detail.path);
});
node_modules
We’re constantly improving our Node/npm compatibility. This release brings a new unstable feature we like to call “BYONM” (”bring your own node modules”). What this means is that you can use whatever package manager of your choice with Deno.
This update makes it easier to use Deno in an existing Node codebase, so give it a try and let us know what you think.
For general Node API compatibility, refer to our docs.
Those three updates are just scratching the surface of 1.38. Here’s a quick list of the rest:
deno run --env
for flexibility in loading .env
filesdeno task
supports head
command (and is cross platform)Deno.test
now works in the REPLDeno.jupyter
namespaceDeno.serve
and using
--unstable-*
flagsArray.fromAsync
and Promise.withResolvers
Phew! Don’t want to read the full announcement? Check out the 2 minute video.
Deno KV becomes more flexible and robust, now that you host it yourself with our new open source binary, denokv
. You can run this on your own server and connect to it via KV Connect.
Here’s a guide to setting up a denokv
server on Fly.io.
We also added continuous backups into S3 or GCS with point-in-time-recovery and live replication support. This means you can retrieve a consistent snapshot of your data at any point in time in the past, run a read-only replica independent of Deno Deploy, or push your data into your favorite data warehouses or lakes like Kafka, BigQuery, and Clickhouse.
Thanks toranoana for the pic!
We partnered with toranoana to organize a one day event filled with awesome talks from the Deno community. Here are the talks from the Deno team:
You all have been active building with and writing about Deno! Here’s a (very incomplete) list of projects and articles.
For more projects and resources (or if you’d like to share yours), join the Discord’s #showcase channel.
And that's it for this issue!
— Andy