mirror of
https://github.com/denoland/deno.git
synced 2024-12-26 17:19:06 -05:00
ab0c33ebf8
This commit stabilizes "Deno.consoleSize()" API. There is one change compared to previous unstable API, in that the API doesn't accept any arguments. Console size is established by querying syscalls for stdio streams at fd 0, 1 and 2. |
||
|---|---|---|
| .. | ||
| 01_build.js | ||
| 01_errors.js | ||
| 01_version.js | ||
| 01_web_util.js | ||
| 06_util.js | ||
| 10_permissions.js | ||
| 11_workers.js | ||
| 12_io.js | ||
| 13_buffer.js | ||
| 30_fs.js | ||
| 30_os.js | ||
| 40_diagnostics.js | ||
| 40_files.js | ||
| 40_fs_events.js | ||
| 40_http.js | ||
| 40_process.js | ||
| 40_read_file.js | ||
| 40_signals.js | ||
| 40_spawn.js | ||
| 40_testing.js | ||
| 40_tty.js | ||
| 40_write_file.js | ||
| 41_prompt.js | ||
| 90_deno_ns.js | ||
| 99_main.js | ||
| README.md | ||
Runtime JavaScript Code
This directory contains Deno runtime code written in plain JavaScript.
Each file is a plain, old script, not ES modules. The reason is that snapshotting ES modules is much harder, especially if one needs to manipulate global scope (like in case of Deno).
Each file is prefixed with a number, telling in which order scripts should be loaded into V8 isolate. This is temporary solution and we're striving not to require specific order (though it's not 100% obvious if that's feasible).
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.