1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-11-21 15:04:11 -05:00
denoland-deno/runtime
cions 881a62869d
fix: android support (#19437)
<!--
Before submitting a PR, please read https://deno.com/manual/contributing

1. Give the PR a descriptive title.

  Examples of good title:
    - fix(std/http): Fix race condition in server
    - docs(console): Update docstrings
    - feat(doc): Handle nested reexports

  Examples of bad title:
    - fix #7123
    - update docs
    - fix bugs

2. Ensure there is a related issue and it is referenced in the PR text.
3. Ensure there are tests that cover the changes.
4. Ensure `cargo test` passes.
5. Ensure `./tools/format.js` passes without changing files.
6. Ensure `./tools/lint.js` passes.
7. Open as a draft PR if your work is still in progress. The CI won't
run
   all steps, but you can add '[ci]' to a commit message to force it to.
8. If you would like to run the benchmarks on the CI, add the 'ci-bench'
label.
-->

---------

Signed-off-by: Matt Mastracci <matthew@mastracci.com>
Co-authored-by: Matt Mastracci <matthew@mastracci.com>
2024-01-10 06:04:14 -07:00
..
examples chore: update copyright to 2024 (#21753) 2024-01-01 19:58:21 +00:00
js refactor: split runtime/98_global_scope.js (#21785) 2024-01-06 14:40:26 +01:00
ops fix: android support (#19437) 2024-01-10 06:04:14 -07:00
permissions fix(ext/node): add fs.cp, fs.cpSync, promises.cp (#21745) 2024-01-05 18:28:33 +05:30
build.rs chore: update copyright to 2024 (#21753) 2024-01-01 19:58:21 +00:00
Cargo.toml chore: forward v1.39.2 release commit to main (#21793) 2024-01-04 23:52:17 +00:00
clippy.toml feat(compile): unstable npm and node specifier support (#19005) 2023-05-10 20:06:59 -04:00
colors.rs chore: update copyright to 2024 (#21753) 2024-01-01 19:58:21 +00:00
errors.rs chore: update copyright to 2024 (#21753) 2024-01-01 19:58:21 +00:00
fmt_errors.rs chore: update copyright to 2024 (#21753) 2024-01-01 19:58:21 +00:00
fs_util.rs chore: update copyright to 2024 (#21753) 2024-01-01 19:58:21 +00:00
inspector_server.rs chore: update copyright to 2024 (#21753) 2024-01-01 19:58:21 +00:00
js.rs chore: update copyright to 2024 (#21753) 2024-01-01 19:58:21 +00:00
lib.rs chore: update copyright to 2024 (#21753) 2024-01-01 19:58:21 +00:00
README.md fix (doc): Typo in runtime/README.md (#20020) 2023-12-13 17:24:32 +00:00
shared.rs refactor: split runtime/98_global_scope.js (#21785) 2024-01-06 14:40:26 +01:00
snapshot.rs fix(ext/node): add fs.cp, fs.cpSync, promises.cp (#21745) 2024-01-05 18:28:33 +05:30
tokio_util.rs chore: update copyright to 2024 (#21753) 2024-01-01 19:58:21 +00:00
web_worker.rs chore: bump deno_core (#21832) 2024-01-10 09:48:40 +05:30
worker.rs chore: bump deno_core (#21832) 2024-01-10 09:48:40 +05:30
worker_bootstrap.rs chore: update copyright to 2024 (#21753) 2024-01-01 19:58:21 +00:00

deno_runtime crate

crates docs

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.