1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-12-27 01:29:14 -05:00
A modern runtime for JavaScript and TypeScript. https://deno.com/
Find a file
Nathan Whitaker d284d1c6a8
fix(ext/node): convert errors from fs.readFile/fs.readFileSync to node format (#26632)
Fixes the original issue reported in #26404. storybook runs into other
errors after this PR (the new errors will be fixed in other PRs).

Some code used by a dependency of storybook does a [string comparison on
the error
message](ce30b2be34/node-src/lib/getConfiguration.ts (L88-L92))
thrown here to check for a file not found error.
2024-11-06 00:36:23 +01:00
.cargo feat: bring back WebGPU (#20812) 2023-12-09 01:19:16 +01:00
.devcontainer chore: remove protoc dep from CI (#26050) 2024-10-07 15:11:31 +00:00
.github 2.0.4 (#26630) 2024-10-30 01:15:35 +01:00
bench_util 2.0.4 (#26630) 2024-10-30 01:15:35 +01:00
cli fix: surface package.json location on dep parse failure (#26665) 2024-11-06 00:36:23 +01:00
ext fix(ext/node): convert errors from fs.readFile/fs.readFileSync to node format (#26632) 2024-11-06 00:36:23 +01:00
resolvers 2.0.4 (#26630) 2024-10-30 01:15:35 +01:00
runtime fix: clamp smi in fast calls by default (#26506) 2024-11-06 00:36:22 +01:00
tests fix: surface package.json location on dep parse failure (#26665) 2024-11-06 00:36:23 +01:00
tools feat: support node-api in denort (#26389) 2024-10-25 02:09:38 +02:00
.dlint.json chore: enable no-console dlint rule (#25113) 2024-08-20 15:14:37 -04:00
.dprint.json fix(fmt): fix several HTML and components issues (#26654) 2024-11-06 00:36:23 +01:00
.editorconfig chore(tests): Remove vestiges of cli/tests folder (#22712) 2024-03-05 13:49:21 -07:00
.gitattributes chore: move cli/tests/ -> tests/ (#22369) 2024-02-10 20:22:13 +00:00
.gitignore chore: move tools/wpt to tests/wpt/runner (#22545) 2024-03-05 00:41:16 +00:00
.gitmodules chore: make remaining submodules shallow (#23441) 2024-04-18 19:45:09 +00:00
.rustfmt.toml chore: update copyright year to 2023 (#17247) 2023-01-02 21:00:42 +00:00
Cargo.lock fix(fmt): fix several HTML and components issues (#26654) 2024-11-06 00:36:23 +01:00
Cargo.toml fix: clamp smi in fast calls by default (#26506) 2024-11-06 00:36:22 +01:00
import_map.json chore: update std submodule (#25595) 2024-09-12 22:32:09 +10:00
LICENSE.md chore: update LICENSE.md to 2024 (#21833) 2024-01-06 19:14:38 -05:00
README.md docs(readme): Add winget instructions (#25136) 2024-10-30 00:15:38 +01:00
Releases.md 2.0.4 (#26630) 2024-10-30 01:15:35 +01:00
rust-toolchain.toml chore: upgrade to rust 1.81.0 (#26261) 2024-10-15 21:40:07 +05:30

Deno

Twitter badge Discord badge YouTube badge

the deno mascot dinosaur standing in the rain

Deno (/ˈdiːnoʊ/, pronounced dee-no) is a JavaScript, TypeScript, and WebAssembly runtime with secure defaults and a great developer experience. It's built on V8, Rust, and Tokio.

Learn more about the Deno runtime in the documentation.

Installation

Install the Deno runtime on your system using one of the commands below. Note that there are a number of ways to install Deno - a comprehensive list of installation options can be found here.

Shell (Mac, Linux):

curl -fsSL https://deno.land/install.sh | sh

PowerShell (Windows):

irm https://deno.land/install.ps1 | iex

Homebrew (Mac):

brew install deno

Chocolatey (Windows):

choco install deno

WinGet (Windows):

winget install --id=DenoLand.Deno

Build and install from source

Complete instructions for building Deno from source can be found in the manual here.

Your first Deno program

Deno can be used for many different applications, but is most commonly used to build web servers. Create a file called server.ts and include the following TypeScript code:

Deno.serve((_req: Request) => {
  return new Response("Hello, world!");
});

Run your server with the following command:

deno run --allow-net server.ts

This should start a local web server on http://localhost:8000.

Learn more about writing and running Deno programs in the docs.

Additional resources

Contributing

We appreciate your help! To contribute, please read our contributing instructions.