Skip to main content

Deno

Discouraged

Not our default choice. We recommend staying on Node.js unless there is a specific requirement.

What is it​

Deno is a secure JavaScript/TypeScript runtime created by Ryan Dahl (the original creator of Node.js). It features built-in TypeScript support, a permissions system, and ships with a standard library. Currently at v2.x.

Why it's not our default​

  • Team expertise — Aliz teams have deep Node.js experience; Deno requires learning a different module system and APIs.
  • Ecosystem maturity — while Deno has improved Node.js compatibility, many npm packages still have edge-case issues or require compatibility layers.
  • Tooling gaps — some CI/CD runners, cloud providers, and deployment targets don't support Deno natively yet.
  • Fragmented knowledge — maintaining expertise in multiple runtimes splits internal knowledge and complicates hiring.

When it makes sense​

  • Deno Deploy target — if you're specifically deploying to Deno Deploy or a platform that requires Deno.
  • Security-first serverless functions — when the built-in permissions model is a genuine project requirement.
  • Client mandates Deno — if the client's existing infrastructure is Deno-based.

Alternative​

Node.js with our standard npm toolchain.

Resources​