1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-12-28 10:09:20 -05:00
denoland-deno/core/README.md
Bartek Iwańczuk f57a2c1e85
refactor(core): rename CoreIsolate to JsRuntime (#7373)
deno_core/
- rename core_isolate.rs to runtime.rs
- rename CoreIsolate to JsRuntime
- rename JSError to JsError
- rename JSStackFrame to JsStackFrame

cli/
- update references from deno_core::CoreIsolate to deno_core::JsRuntime
- rename deno_core::JSError to deno_core::JsError
- rename fmt_errors::JSError to fmt_errors::JsError
2020-09-06 21:44:29 +02:00

1.3 KiB

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 is modeled as a Future<Item=(), Error=JsError> which completes once all of its ops have completed.

In order to bind Rust functions into JavaScript, use the Deno.core.dispatch() function to trigger the "dispatch" callback in Rust. The user is responsible for encoding both the request and response into a Uint8Array.

Documentation for this crate is thin at the moment. Please see http_bench_bin_ops.rs and http_bench_json_ops.rs as a simple example of usage.

TypeScript support and a lot of other functionality is not available at this layer. See the CLI for that.