b183737fc9
Fixes #6259. Adds the location for v8 syntax errors to the message (`message += " at {location}"`) when rethrowing them for dynamic imports. Discussing with @bartlomieju on discord I proposed just preserving v8's error and not reconstructing it, allowing the standard stack trace to just point to the syntax error instead of the dynamic import. But on further thought this way has parity with SWC's syntax errors + has the advantage of showing both the syntax error and dynamic import location. ```ts // temp.js await import("./temp2.js"); // temp2.js function foo() { await Promise.resolve(); } // Before: // error: Uncaught (in promise) SyntaxError: Unexpected reserved word // await import("./temp2.js"); // ^ // at async file:///.../temp.js:1:1 // After: // error: Uncaught (in promise) SyntaxError: Unexpected reserved word at file:///.../temp2.js:2:3 // await import("./temp2.js"); // ^ // at async file:///.../temp.js:1:1 ``` |
||
|---|---|---|
| .. | ||
| examples | ||
| 00_primordials.js | ||
| 01_core.js | ||
| 02_error.js | ||
| async_cancel.rs | ||
| async_cell.rs | ||
| bindings.rs | ||
| Cargo.toml | ||
| encode_decode_test.js | ||
| error.rs | ||
| error_builder_test.js | ||
| error_codes.rs | ||
| extensions.rs | ||
| fast_string.rs | ||
| flags.rs | ||
| gotham_state.rs | ||
| icudtl.dat | ||
| inspector.rs | ||
| internal.d.ts | ||
| io.rs | ||
| lib.deno_core.d.ts | ||
| lib.rs | ||
| module_specifier.rs | ||
| modules.rs | ||
| normalize_path.rs | ||
| ops.rs | ||
| ops_builtin.rs | ||
| ops_builtin_v8.rs | ||
| ops_metrics.rs | ||
| README.md | ||
| realm.rs | ||
| resources.rs | ||
| runtime.rs | ||
| serialize_deserialize_test.js | ||
| snapshot_util.rs | ||
| source_map.rs | ||
| task_queue.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 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.