mirror of
https://github.com/denoland/deno.git
synced 2024-12-27 09:39:08 -05:00
594a99817c
This PR removes the public Deno.tracing.Span API. We are not confident we can ship an API that is better than the `@opentelemetry/api` API, because V8 CPED does not support us using `using` to manage span context. If this changes, we can revisit this decision. For now, users wanting custom spans can instrument their code using the `@opentelemetry/api` API and `@deno/otel`. This PR also speeds up the OTEL trace generation by a 30% by using Uint8Array instead of strings for the trace ID and span ID. |
||
|---|---|---|
| .. | ||
| 01_errors.js | ||
| 01_version.ts | ||
| 06_util.js | ||
| 10_permissions.js | ||
| 11_workers.js | ||
| 30_os.js | ||
| 40_fs_events.js | ||
| 40_process.js | ||
| 40_signals.js | ||
| 40_tty.js | ||
| 41_prompt.js | ||
| 90_deno_ns.js | ||
| 98_global_scope_shared.js | ||
| 98_global_scope_window.js | ||
| 98_global_scope_worker.js | ||
| 99_main.js | ||
| README.md | ||
| telemetry.ts | ||
Runtime JavaScript Code
This directory contains Deno runtime code written in plain JavaScript.
Each file is an ES module and is prefixed with a number, telling in which order scripts should be loaded into V8 isolate.
Deno Web APIs
This directory facilities Web APIs that are available in Deno.
Please note, that some implementations might not be completely aligned with specification.
Some Web APIs are using ops under the hood, eg. console, performance.
Implemented Web APIs
- Blob: for representing opaque binary data.
- Console: for logging purposes.
- CustomEvent,
EventTarget
and
EventListener:
to work with DOM events.
- Implementation notes: There is no DOM hierarchy in Deno, so there is no tree for Events to bubble/capture through.
- fetch, Request, Response, Body and Headers: modern Promise-based HTTP Request API.
- location and Location.
- FormData: access
to a
multipart/form-dataserialization. - Performance: retrieving current time with a high precision.
- setTimeout, setInterval, clearTimeout: scheduling callbacks in future and clearInterval.
- Stream for creating, composing, and consuming streams of data.
- URL and URLSearchParams: to construct and parse URLSs.
- Worker: executing
additional code in a separate thread.
- Implementation notes: Blob URLs are not supported, object ownership cannot be transferred, posted data is serialized to JSON instead of structured cloning.