We got many updates this month, including a faster Deno in its 1.43 release, several JSR announcements and resources, and case studies from Netlify and Slack. Let's dive on in.
In 1.43, we added many performance improvements, such as code caching, more efficient memory usage in our language server protocol, and more. Now, startup time in Deno is almost 2x faster than in Node, depending on program size. On top of that, our LSP auto-completion times are reduced from 6-8 seconds to under a second in large code bases.
Watch the 2min video highlighting features of 1.43.
In addition to performance improvements, 1.43 ships with improved Node.js and npm compatibility, quality of life improvements in deno.json
, the new deno serve
subcommand, and more.
Read the full announcement or watch the video ⇒
Despite package managers — such as yarn and pnpm — improving the package installation experience, the underlying registry has made little innovation. (Its last notable update was a “files” tab added years ago.)
In this article, Ryan asserts that JavaScript registry’s lack of innovation is what JSR sets out to address. JSR, adhering to modern web standards such as ESM as well as natively supporting fast growing TypeScript, aims to push the JavaScript ecosystem — known for its vibrant evolution — forward.
We’re thrilled to announce new packages on JSR, including Hookdeck, Neon, and the Deno Standard Library:
Did you add a package to JSR recently and would like us to feature you? Reply to this email and we’ll respond.
If you’re authoring JavaScript packages in 2024, then this blog post is for you. There are a lot of modern tooling (JSDoc!) that can help you write comprehensive documentation for your users that fit into your workflow and theirs.
While low code solutions can offer your users value by reducing development effort and complexity, it can’t solve all problems. As your platforms’ capabilities grow with more integrations, your users will inevitably ask for more customization. Instead of trying to anticipate and build for each use case, you can simply offer an “escape hatch” — let your users write, host, and run custom code specifically designed to solve their problems.
This blog post digs into 3 product scenarios in which an “escape hatch” works great to solve users’ needs.
Here are some projects shared in our #showcase channel in Discord:
nudd
, a simple way to manage Deno dependencieslibllama
, llama.ccp bindings for JavaScriptbyte
, a fast, minimal micro framework, faster than Honopaska-ovo
, add easter eggs to your web sitesnomake
, a build system that supports multiple programming languages, static type checking, intellisense and distributed buildingkv
, a runtime-agnostic, efficient KV storeJo Franchetti will be at EMF and Lead Dev Conf London. If you’re at either of those, come say hi and grab some Deno merch!
.tsconfig
And that’s it for this issue! If you think someone else might find this useful, please forward it to them.
— Andy