Find a file
Nathan Whitaker 51f5f5789b
feat(add): Add npm packages to package.json if present (#25477)
Closes https://github.com/denoland/deno/issues/25321

Ended up being a larger refactoring, since we're now juggling
(potentially) two config files in the same `add`, instead of choosing
one. I don't love the shape of the code, but I think it's good enough

Some smaller side improvements:
- `deno remove` supports `jsonc`
- `deno install --dev` will be a really simple change
- if `deno remove` removes the last import/dependency in the
`imports`/`dependencies`/`devDependencies` field, it removes the field
instead of leaving an empty object
2024-09-06 17:18:13 +00: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: forward v1.46.3 release commit to main (#25425) 2024-09-04 17:16:24 +00:00
bench_util chore: forward v1.46.3 release commit to main (#25425) 2024-09-04 17:16:24 +00:00
cli feat(add): Add npm packages to package.json if present (#25477) 2024-09-06 17:18:13 +00:00
ext feat(add): Add npm packages to package.json if present (#25477) 2024-09-06 17:18:13 +00:00
runtime fix(runtime): use more null proto objects again (#25040) 2024-09-06 12:52:59 +02:00
tests feat(add): Add npm packages to package.json if present (#25477) 2024-09-06 17:18:13 +00:00
tools BREAKING(buffer): remove Deno.Buffer (#25441) 2024-09-06 18:28:05 +10:00
.dlint.json chore: enable no-console dlint rule (#25113) 2024-08-20 15:14:37 -04:00
.dprint.json fix: upgrade deno_ast 0.42 (#25313) 2024-08-30 17:12:13 -04: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 feat(add): Add npm packages to package.json if present (#25477) 2024-09-06 17:18:13 +00:00
Cargo.toml feat(add): Add npm packages to package.json if present (#25477) 2024-09-06 17:18:13 +00:00
import_map.json chore: update to std@2024.07.19 (#24715) 2024-07-25 15:30:28 +10:00
LICENSE.md chore: update LICENSE.md to 2024 (#21833) 2024-01-06 19:14:38 -05:00
README.md chore: update references to deno_std to use JSR (#23239) 2024-04-10 17:26:35 -04:00
Releases.md chore: forward v1.46.3 release commit to main (#25425) 2024-09-04 17:16:24 +00:00
rust-toolchain.toml chore: Rust 1.80.1 (#25089) 2024-08-18 22:24:56 -04: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.