1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-12-22 07:14:47 -05:00
denoland-deno/runtime
Julien Cayzac ca64771257
fix(unstable): Honor granular unstable flags in js runtime (#21466)
This fixes #21434 for `BroadcastChannel` and `WebSocketStream`.
`--unstable` still enable both, but granular unstable flags now also
work:

* `--unstable-net` now enables `WebSocketStream`.
* `--unstable-broadcast-channel` now enables `BroadcastChannel`.
* Additionally, there are now tests for all granular unstable flags.
Since `unsafe-proto` already had tests, so I didn't add any for this
one.

It also introduces a map to keep track of granular unstable ids without
having to sync multiple places.
2023-12-08 14:24:49 +01:00
..
examples refactor: rewrite some ops to op2 macro (#20603) 2023-09-21 08:08:23 -06:00
js fix(unstable): Honor granular unstable flags in js runtime (#21466) 2023-12-08 14:24:49 +01:00
ops fix(ext/node): fix os.freemem (#21347) 2023-11-30 22:06:01 +09:00
permissions perf(node/fs): faster existsSync when not exists (#21458) 2023-12-04 21:05:40 +00:00
build.rs refactor: snapshotting of runtime/ and cli/ (#21430) 2023-12-02 23:40:27 +00:00
Cargo.toml chore: forward v1.38.5 release commit to main (#21472) 2023-12-06 00:53:16 +00:00
clippy.toml feat(compile): unstable npm and node specifier support (#19005) 2023-05-10 20:06:59 -04:00
colors.rs fix: Deno.noColor should not be true when NO_COLOR is empty string (#21275) 2023-11-20 15:58:22 -05:00
errors.rs chore(ext/kv): update denokv crates (#21357) 2023-11-28 21:04:07 -08:00
fmt_errors.rs chore: bump deno_core and update tests (#21467) 2023-12-06 17:02:52 -07:00
fs_util.rs feat(compile): unstable npm and node specifier support (#19005) 2023-05-10 20:06:59 -04:00
inspector_server.rs fix(cli): Support using both --watch and --inspect at the same time (#20660) 2023-10-06 23:33:14 +02:00
js.rs build: allow disabling snapshots for dev (#20048) 2023-08-06 01:47:15 +02:00
lib.rs refactor: snapshot module for deno_runtime (#21162) 2023-11-14 12:15:49 +00:00
README.md chore: fix decendents in runtime readme (#9718) 2021-03-08 13:23:46 +01:00
shared.rs refactor(runtime): factor out code between build.rs and worker.rs (#20299) 2023-08-28 15:30:46 -06:00
snapshot.rs perf(node/fs): faster existsSync when not exists (#21458) 2023-12-04 21:05:40 +00:00
tokio_util.rs fix(ext/web): add stream tests to detect v8slice split bug (#20253) 2023-08-23 17:03:05 -06:00
web_worker.rs chore: use primordials in 40_testing.js (#21422) 2023-12-08 08:33:25 +01:00
worker.rs chore: use primordials in 40_testing.js (#21422) 2023-12-08 08:33:25 +01:00
worker_bootstrap.rs perf: static bootstrap options in snapshot (#21213) 2023-11-15 13:25:55 +01: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 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.