Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

deno

deno: A modern runtime for JavaScript and TypeScript.

What problem it solves

Deno provides a runtime for JavaScript, TypeScript, and WebAssembly with secure defaults and a developer experience designed for building and running applications across platforms. It also provides multiple installation paths and guidance for creating a first web server.

Key features

  • Secure runtime defaults — The runtime includes secure defaults and explicit permission controls for capabilities such as network access, file reads, and other operations.

    Source: README, runtime/permissions

  • JavaScript and TypeScript execution — Deno runs JavaScript, TypeScript, and WebAssembly programs. Its first-program example uses TypeScript directly with the Deno.serve API.

    Source: README, runtime

  • Web server support — The runtime can serve HTTP responses through Deno.serve, and the documented example starts a local web server from a TypeScript file.

    Source: README, ext/http, ext/net

  • Multiple installation options — The README documents installation for macOS, Linux, and Windows through shell scripts, PowerShell, Homebrew, Chocolatey, WinGet, and Scoop.

    Source: README

  • Standard library and package resources — The project points developers to an officially supported standard library and JSR, described as an open-source package registry for modern JavaScript and TypeScript.

    Source: README

Quick start

Copied verbatim from the project's README.

curl -fsSL https://deno.land/install.sh | sh
Deno.serve((_req: Request) => {
  return new Response("Hello, world!");
});
deno run --allow-net server.ts

Who it may suit

This runtime may suit developers who want to build web servers or run JavaScript and TypeScript with secure defaults. It may also suit teams looking for a documented installation path across major desktop platforms.

Topics to discuss

  • Which permission model would make secure defaults clearer for new applications?

  • How can the first-program experience better guide developers toward common application patterns?

  • Which ecosystem resources should receive more emphasis in the project documentation?


Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/denoland/deno#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.

github.comhttps://github.com/denoland/deno

Comments

…