foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-11-21 15:04:11 -05:00
Code Issues Packages 1 Wiki Activity
denoland-deno/runtime
History
Bartek Iwańczuk 24c3c96958
feat: granular --unstable-* flags (#20968) 
This commit adds granular `--unstable-*` flags:
- "--unstable-broadcast-channel"
- "--unstable-ffi"
- "--unstable-fs"
- "--unstable-http"
- "--unstable-kv"
- "--unstable-net"
- "--unstable-worker-options"
- "--unstable-cron"

These flags are meant to replace a "catch-all" flag - "--unstable", that
gives a binary control whether unstable features are enabled or not. The
downside of this flag that allowing eg. Deno KV API also enables the FFI
API (though the latter is still gated with a permission).

These flags can also be specified in `deno.json` file under `unstable`
key.

Currently, "--unstable" flag works the same way - I will open a follow
up PR that will print a warning when using "--unstable" and suggest to use
concrete "--unstable-*" flag instead. We plan to phase out "--unstable"
completely in Deno 2.
2023-11-01 23:15:08 +01:00
..
examples refactor: rewrite some ops to op2 macro (#20603) 2023-09-21 08:08:23 -06:00
js feat: granular --unstable-* flags (#20968) 2023-11-01 23:15:08 +01:00
ops feat: granular --unstable-* flags (#20968) 2023-11-01 23:15:08 +01:00
permissions refactor: remove TimersPermissions::check_unstable (#20831) 2023-10-09 02:08:10 +02:00
build.rs feat(cron) implement Deno.cron() (#21019) 2023-11-01 11:57:55 -07:00
Cargo.toml feat(cron) implement Deno.cron() (#21019) 2023-11-01 11:57:55 -07:00
clippy.toml feat(compile): unstable npm and node specifier support (#19005) 2023-05-10 20:06:59 -04:00
colors.rs chore(cli): remove atty crate (#20275) 2023-08-25 07:43:07 -06:00
errors.rs chore: update ext/kv to use denokv_* crates (#20986) 2023-10-31 11:13:57 +00:00
fmt_errors.rs refactor: remove ext/console/01_colors.js (#18927) 2023-04-30 09:11:37 +00: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 feat(cron) implement Deno.cron() (#21019) 2023-11-01 11:57:55 -07: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
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 feat(cron) implement Deno.cron() (#21019) 2023-11-01 11:57:55 -07:00
worker.rs feat(cron) implement Deno.cron() (#21019) 2023-11-01 11:57:55 -07:00
worker_bootstrap.rs feat: granular --unstable-* flags (#20968) 2023-11-01 23:15:08 +01:00

README.md

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.