355d8994b2
Some checks failed
ci / pre-build (push) Has been cancelled
ci / test debug linux-aarch64 (push) Has been cancelled
ci / test release linux-aarch64 (push) Has been cancelled
ci / test debug macos-aarch64 (push) Has been cancelled
ci / test release macos-aarch64 (push) Has been cancelled
ci / bench release linux-x86_64 (push) Has been cancelled
ci / test debug linux-x86_64 (push) Has been cancelled
ci / test release linux-x86_64 (push) Has been cancelled
ci / test debug macos-x86_64 (push) Has been cancelled
ci / test release macos-x86_64 (push) Has been cancelled
ci / test debug windows-x86_64 (push) Has been cancelled
ci / test release windows-x86_64 (push) Has been cancelled
ci / lint debug linux-x86_64 (push) Has been cancelled
ci / lint debug macos-x86_64 (push) Has been cancelled
ci / lint debug windows-x86_64 (push) Has been cancelled
ci / build libs (push) Has been cancelled
ci / publish canary (push) Has been cancelled
Solution for: https://github.com/denoland/deno/issues/31080 Modern reqwest (0.12+) can safely share clients across tokio runtimes. Because it uses the current runtime's executor instead of spawning background threads. Using a single shared client prevents resource leaks when worker threads terminate. ## Context It seems that we started to use one client per thread because hyper and reqwest was not safe to share across tokio runtimes (https://github.com/denoland/deno/pull/23699). But seems it's fixed at latest reqwest versions (https://github.com/seanmonstar/reqwest/issues/1148#issuecomment-3120048532). This PR is using one client again, as we now already use the version of reqwest with this fix. |
||
|---|---|---|
| .. | ||
| features | ||
| js | ||
| ops | ||
| permissions | ||
| subprocess_windows | ||
| Cargo.toml | ||
| clippy.toml | ||
| code_cache.rs | ||
| coverage.rs | ||
| fmt_errors.rs | ||
| inspector_server.rs | ||
| js.rs | ||
| lib.rs | ||
| permissions.rs | ||
| README.md | ||
| shared.rs | ||
| snapshot.rs | ||
| snapshot_info.rs | ||
| tokio_util.rs | ||
| transpile.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 the
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.