1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-12-23 15:49:44 -05:00
A modern runtime for JavaScript and TypeScript. https://deno.com/
Find a file
MujahedSafaa 94a5eaf5b8
fix(ext/console): Error Cause Not Inspect-Formatted when printed (#24526)
This pull request addresses an issue where the Error.cause property was
not formatted correctly when printed using console.log, leading to
confusion.

solution:
Implemented a fix to ensure that Error.cause is formatted properly when
printed by console.log, and the fix done by using JSON.stringify

This PR fixes https://github.com/denoland/deno/issues/23416

---------

Signed-off-by: MujahedSafaa <168719085+MujahedSafaa@users.noreply.github.com>
2024-07-22 22:48:39 +02: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 dependencies (#24565) 2024-07-22 22:47:08 +02:00
bench_util 1.45.2 (#24561) 2024-07-12 16:04:46 -04:00
cli fix(cli): add NAPI support in standalone mode (#24642) 2024-07-22 22:48:39 +02:00
ext fix(ext/console): Error Cause Not Inspect-Formatted when printed (#24526) 2024-07-22 22:48:39 +02:00
runtime fix: CFunctionInfo and CTypeInfo leaks (#24634) 2024-07-22 22:48:39 +02:00
tests fix(ext/console): Error Cause Not Inspect-Formatted when printed (#24526) 2024-07-22 22:48:39 +02:00
tools chore: include current versions more in release checklist (#24562) 2024-07-22 22:46:39 +02:00
.dlint.json chore: update dlint to v0.37.0 for GitHub Actions (#17295) 2023-01-16 17:17:18 +01:00
.dprint.json fix(fmt): was sometimes putting comments in front of commas in parameter lists (#24650) 2024-07-22 22:47:58 +02: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: make vendor cache manifest more deterministic (#24658) 2024-07-22 22:48:39 +02:00
Cargo.toml fix: make vendor cache manifest more deterministic (#24658) 2024-07-22 22:48:39 +02: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 1.45.2 (#24561) 2024-07-12 16:04:46 -04:00
rust-toolchain.toml chore: upgrade to rust 1.79 (#24207) 2024-06-14 17:10:57 +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

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.