e511022c74
Code run within Deno-mode and Node-mode should have access to a slightly different set of globals. Previously this was done through a compile time code-transform for Node-mode, but this is not ideal and has many edge cases, for example Node's globalThis having a different identity than Deno's globalThis. This commit makes the `globalThis` of the entire runtime a semi-proxy. This proxy returns a different set of globals depending on the caller's mode. This is not a full proxy, because it is shadowed by "real" properties on globalThis. This is done to avoid the overhead of a full proxy for all globalThis operations. The globals between Deno-mode and Node-mode are now properly segregated. This means that code running in Deno-mode will not have access to Node's globals, and vice versa. Deleting a managed global in Deno-mode will NOT delete the corresponding global in Node-mode, and vice versa. --------- Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com> Co-authored-by: Aapo Alasuutari <aapo.alasuutari@gmail.com> |
||
|---|---|---|
| .. | ||
| examples | ||
| js | ||
| ops | ||
| permissions | ||
| build.rs | ||
| Cargo.toml | ||
| clippy.toml | ||
| colors.rs | ||
| errors.rs | ||
| fmt_errors.rs | ||
| fs_util.rs | ||
| inspector_server.rs | ||
| js.rs | ||
| lib.rs | ||
| README.md | ||
| tokio_util.rs | ||
| web_worker.rs | ||
| worker.rs | ||
| worker_bootstrap.rs | ||
deno_runtime crate
This is a slim version of the Deno CLI which removes typescript integration and various tooling (like lint and doc). Basically only JavaScript execution with Deno's operating system bindings (ops).
Stability
This crate is built using battle-tested modules that were originally in deno
crate, however the API of this crate is subject to rapid and breaking changes.
MainWorker
The main API of this crate is MainWorker. MainWorker is a structure
encapsulating deno_core::JsRuntime with a set of ops used to implement Deno
namespace.
When creating a MainWorker implementors must call MainWorker::bootstrap to
prepare JS runtime for use.
MainWorker is highly configurable and allows to customize many of the
runtime's properties:
- module loading implementation
- error formatting
- support for source maps
- support for V8 inspector and Chrome Devtools debugger
- HTTP client user agent, CA certificate
- random number generator seed
Worker Web API
deno_runtime comes with support for Worker Web API. The Worker API is
implemented using WebWorker structure.
When creating a new instance of MainWorker implementors must provide a
callback function that is used when creating a new instance of Worker.
All WebWorker instances are descendents of MainWorker which is responsible
for setting up communication with child worker. Each WebWorker spawns a new OS
thread that is dedicated solely to that worker.