Find a file
Nathan Whitaker 99720d0713
chore: Make jupyter integration tests less flaky and avoid hang (#23134)
There's a TOCTOU issue that can happen when selecting unused ports for
the server to use (we get assigned an unused port by the OS, and between
then and when the server actually binds to the port another test steals
it). Improve this by checking if the server existed soon after setup,
and if so we retry starting it. Client connection can also fail
spuriously (in local testing) so added a retry mechanism.

This also fixes a hang, where if the server exited (almost always due to
the issue described above) before we connected to it, attempting to
connect our client ZMQ sockets to it would just hang. To resolve this, I
added a timeout so we can't wait forever.
2024-03-29 23:23:48 -07:00
.cargo feat: bring back WebGPU (#20812) 2023-12-09 01:19:16 +01:00
.devcontainer fix(devcontainer): moved settings to customizations/vscode (#21512) 2023-12-19 13:29:39 +01:00
.github 1.42.0 (#23105) 2024-03-28 01:47:33 +01:00
bench_util 1.42.0 (#23105) 2024-03-28 01:47:33 +01:00
cli fix(lsp): implement missing ts server host apis (#23131) 2024-03-29 20:00:58 +00:00
ext fix(node): remove unwrap in op_require_node_module_paths (#23114) 2024-03-28 17:51:41 -04:00
runtime 1.42.0 (#23105) 2024-03-28 01:47:33 +01:00
tests chore: Make jupyter integration tests less flaky and avoid hang (#23134) 2024-03-29 23:23:48 -07:00
tools feat(init): use jsr specifier for @std/assert (#23073) 2024-03-27 18:51:52 +01:00
.dlint.json chore: update dlint to v0.37.0 for GitHub Actions (#17295) 2023-01-16 17:17:18 +01:00
.dprint.json chore(tests): Remove vestiges of cli/tests folder (#22712) 2024-03-05 13:49:21 -07: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: move test_util/wpt to tests/wpt/suite (#22412) 2024-02-16 03:32:28 +00:00
.rustfmt.toml chore: update copyright year to 2023 (#17247) 2023-01-02 21:00:42 +00:00
Cargo.lock 1.42.0 (#23105) 2024-03-28 01:47:33 +01:00
Cargo.toml 1.42.0 (#23105) 2024-03-28 01:47:33 +01:00
LICENSE.md chore: update LICENSE.md to 2024 (#21833) 2024-01-06 19:14:38 -05:00
README.md chore: Fix typo in README (#21354) 2023-11-27 21:43:35 +00:00
Releases.md 1.42.0 (#23105) 2024-03-28 01:47:33 +01:00
rust-toolchain.toml chore: update to Rust 1.76 (#22376) 2024-02-12 03:00:33 +00:00

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

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.