1cd2267500
This commit changes "deno info" subcommand logic. - Modules are no longer loaded into V8 isolate - analysis is done using ModuleGraph. - Removed deno_core::Deps structure. - Modules are no longer type-checked and transpiled - "compiled" file is shown only if it is already available. - Added number of unique dependencies for root module. - Changed tree output: - file size is shown next to the dependency - repeated dependencies are marked with "*" - used less spaces in prefix to save terminal width |
||
---|---|---|
.. | ||
examples | ||
basic_state.rs | ||
bindings.rs | ||
Cargo.toml | ||
core.js | ||
core_test.js | ||
encode_decode_test.js | ||
errors.rs | ||
flags.rs | ||
lib.rs | ||
module_specifier.rs | ||
modules.rs | ||
normalize_path.rs | ||
ops.rs | ||
plugin_api.rs | ||
README.md | ||
resources.rs | ||
runtime.rs | ||
shared_queue.rs | ||
zero_copy_buf.rs |
Deno Core Crate
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.