Skip to content

Files

Latest commit

Mar 16, 2023
f64adbe · Mar 16, 2023

History

History
This branch is 238 commits ahead of, 5306 commits behind denoland/deno:main.

core

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Mar 16, 2023
Mar 16, 2023
Mar 16, 2023
Jan 26, 2023
Mar 16, 2023
Oct 21, 2022
Jan 5, 2023
Feb 11, 2023
Mar 10, 2023
Jan 2, 2023
Mar 10, 2023
Jan 2, 2023
Feb 12, 2023
Mar 10, 2023
Jan 2, 2023
Mar 16, 2023
Feb 7, 2023
Feb 7, 2023
Mar 16, 2023
Jan 2, 2023
Mar 10, 2023
Mar 16, 2023
Mar 16, 2023
Mar 10, 2023
Jan 2, 2023
Mar 16, 2023
Mar 10, 2023
Mar 16, 2023
Jan 15, 2023
Jan 2, 2023
Mar 16, 2023
Jan 2, 2023
Mar 10, 2023
Jan 2, 2023
Mar 10, 2023

Deno Core Crate

crates docs

The main dependency of this crate is rusty_v8, which provides the V8-Rust bindings.

This Rust crate contains the essential V8 bindings for Deno's command-line interface (Deno CLI). The main abstraction here is the JsRuntime which provides a way to execute JavaScript.

The JsRuntime implements an event loop abstraction for the executed code that keeps track of all pending tasks (async ops, dynamic module loads). It is user's responsibility to drive that loop by using JsRuntime::run_event_loop method - it must be executed in the context of Rust's future executor (eg. tokio, smol).

Rust functions can be registered in JavaScript using deno_core::Extension. Use the Deno.core.ops.op_name() and Deno.core.opAsync("op_name", ...) functions to trigger the op function callback. A conventional way to write ops is using the deno_ops crate.

Documentation for this crate is thin at the moment. Please see hello_world.rs and http_bench_json_ops.rs as examples of usage.

TypeScript support and lots of other functionality are not available at this layer. See the CLI for that.