mirror of
https://github.com/denoland/deno.git
synced 2024-12-22 15:24:46 -05:00
f3bde1d53b
This commit splits `Deno.upgradeHttp` into two different APIs, because the same API is currently overloaded with two different functions. Flash requests upgrade immediately, with no need to return a `Response` object. Instead you have to manually write the response to the socket. Hyper requests only upgrade once a `Response` object has been sent. These two behaviours are now split into `Deno.upgradeHttp` and `Deno.upgradeHttpRaw`. The latter is flash only. The former only supports hyper requests at the moment, but can be updated to support flash in the future. Additionally this removes `void | Promise<void>` as valid return types for the handler function. If one wants to use `Deno.upgradeHttpRaw`, they will have to type cast the handler signature - the signature is meant for the 99.99%, and should not be complicated for the 0.01% that use `Deno.upgradeHttpRaw()`. |
||
|---|---|---|
| .. | ||
| 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.