1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2025-01-09 23:58:23 -05:00
A modern runtime for JavaScript and TypeScript. https://deno.com/
Find a file
Yoshiya Hinosawa 9ad0d4c3db
fix(ext/http): improve error message when underlying resource of request body unavailable (#27463)
The error message is currently `Bad Resource ID`. This commit changes it to
`Cannot read request body as underlying resource unavailable`

closes #27133
2025-01-06 16:12:21 +09: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 chore: fix windows pre release CI job (#27518) 2024-12-31 23:08:15 +00:00
bench_util chore: Happy New Year 2025 (#27509) 2024-12-31 19:12:39 +00:00
cli fix(kv): improve backoff error message and inline documentation (#27537) 2025-01-04 00:04:14 +01:00
ext fix(ext/http): improve error message when underlying resource of request body unavailable (#27463) 2025-01-06 16:12:21 +09:00
resolvers chore: Happy New Year 2025 (#27509) 2024-12-31 19:12:39 +00:00
runtime refactor: remove use of home crate (#27516) 2025-01-02 10:06:35 -05:00
tests fix(ext/http): improve error message when underlying resource of request body unavailable (#27463) 2025-01-06 16:12:21 +09:00
tools refactor(node/npm): separate out permission check from npm resolvers (#27511) 2025-01-02 10:05:52 -05:00
.dlint.json chore: enable no-console dlint rule (#25113) 2024-08-20 15:14:37 -04:00
.dprint.json chore: cargo fmt - turn on group_imports=StdExternalCrate (#26646) 2024-12-31 12:13:39 -05: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(check): move module not found errors to typescript diagnostics (#27533) 2025-01-03 21:49:56 +00:00
Cargo.toml fix(check): move module not found errors to typescript diagnostics (#27533) 2025-01-03 21:49:56 +00:00
import_map.json chore: update std submodule (#25595) 2024-09-12 22:32:09 +10:00
LICENSE.md chore: Happy New Year 2025 (#27509) 2024-12-31 19:12:39 +00:00
README.md docs(readme): Add winget instructions (#25136) 2024-10-26 23:31:44 +00:00
Releases.md chore: forward v2.1.4 release commit to main (#27329) 2024-12-11 12:47:31 +00:00
rust-toolchain.toml chore: upgrade to rust 1.82 and LLVM 19 (#26615) 2024-11-01 16:13:02 +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.