1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-12-22 15:24:46 -05:00
A modern runtime for JavaScript and TypeScript. https://deno.com/
Find a file
Matt Mastracci 4104a674c7
fix(ext/ffi): improve error messages in FFI module (#17786)
Fixes denoland#16922.

The error messages in the `ffi` module are somewhat cryptic when passing
functions that have invalid `parameters` or `result` type strings. While
the generated serializer for the `ForeignFunction` struct correctly
outputs a correct and verbose message, the user sees a far less helpful
`data did not match any variant` message instead.

The underlying cause appears to be the fallback message in the
auto-derived deserializer for untagged enums [1] generated as a result
of `ForeignSymbol` being marked as `#[serde(untagged)]` [2]. Passing an
unexpected value for `NativeType` causes it to error out while
attempting to deserialize both enum variants -- once because it's not a
match for the `ForeignStatic` variant, and once because the
`ForeignFunction` deserializer rejects the invalid type for the
parameters/return type. This is currently open as [serde
#773](https://github.com/serde-rs/serde/issues/773), and not a trivial
exercise to fix generically.

[1]
https://github.com/serde-rs/serde/blob/v0.9.7/serde_derive/src/de.rs#L730
[2] https://github.com/denoland/deno/blob/main/ext/ffi/dlfcn.rs#L102
[3] https://github.com/serde-rs/serde/issues/773

Note that the auto-generated deserializer for untagged enums uses a
private API to buffer deserializer content that we don't have access to.
Instead, we can make use of the `serde_value` crate to buffer the
values. This can likely be removed once the official buffering API lands
(see [4] and [5]). In addition, this crate pulls in `serde_json` as a
cheap way to test that the deserializer works properly.

[4] https://github.com/serde-rs/serde/issues/741
[5] https://github.com/serde-rs/serde/pull/2348
2023-02-15 09:41:59 +05:30
.cargo fix: upgrade deno_ast to 0.23 (#17269) 2023-01-04 18:54:54 -05:00
.devcontainer chore: update devcontainer configuration (#15751) 2022-09-03 02:21:41 +02:00
.github chore: upgrade to Rust 1.67 (#17548) 2023-01-27 10:43:16 -05:00
bench_util refactor: internal runtime code TS support (#17672) 2023-02-08 22:40:18 +01:00
cli feat(ext/node): embed std/node into the snapshot (#17724) 2023-02-14 17:38:45 +01:00
core chore(build): don't compress TSC snapshot in debug build (#17772) 2023-02-14 02:46:32 +01:00
ext fix(ext/ffi): improve error messages in FFI module (#17786) 2023-02-15 09:41:59 +05:30
lockfile chore: forward v1.30.3 release commit to main (#17677) 2023-02-07 04:15:38 +00:00
ops chore: forward v1.30.3 release commit to main (#17677) 2023-02-07 04:15:38 +00:00
runtime feat(ext/node): embed std/node into the snapshot (#17724) 2023-02-14 17:38:45 +01:00
serde_v8 chore: forward v1.30.3 release commit to main (#17677) 2023-02-07 04:15:38 +00:00
test_ffi perf(ext/ffi): Revert UTF-8 validity check from getCString (#17741) 2023-02-12 18:42:35 +02:00
test_napi feat(node): stabilize Node-API (#17553) 2023-02-14 15:53:00 +01:00
test_util feat(install): follow redirects for urls with no path (#17449) 2023-02-10 10:11:11 -05:00
third_party@b057caf233 refactor: deno_graph 0.43 upgrade (#17692) 2023-02-09 22:00:23 -05:00
tools refactor: deno_graph 0.43 upgrade (#17692) 2023-02-09 22:00:23 -05:00
.dlint.json chore: update dlint to v0.37.0 for GitHub Actions (#17295) 2023-01-16 17:17:18 +01:00
.dprint.json fix(fmt): semiColons: false - handle prop with following generator and do while with no block body (#17567) 2023-01-28 10:06:37 -05:00
.editorconfig editorconfig: Don't insert final newline in .out files (#1686) 2019-02-07 11:31:49 -05:00
.gitattributes fix(test): support typechecking docs with CRLF line endings (#12748) 2021-11-15 09:58:04 -05:00
.gitignore feat(npm): implement Node API (#13633) 2022-10-05 19:36:44 +05:30
.gitmodules feat(ext/ffi): Implement FFI fast-call trampoline with Dynasmrt (#15305) 2022-09-07 12:23:56 +05:30
.rustfmt.toml chore: update copyright year to 2023 (#17247) 2023-01-02 21:00:42 +00:00
Cargo.lock fix(ext/ffi): improve error messages in FFI module (#17786) 2023-02-15 09:41:59 +05:30
Cargo.toml chore: upgrade rusty_v8 to 0.63.0 (#17705) 2023-02-10 12:40:03 +00:00
LICENSE.md chore: update copyright year to 2023 (#17247) 2023-01-02 21:00:42 +00:00
README.md docs: use irm instead of iwr -useb (#15474) 2022-08-15 10:05:29 -04:00
Releases.md chore: forward v1.30.3 release commit to main (#17677) 2023-02-07 04:15:38 +00:00
rust-toolchain.toml chore: upgrade to Rust 1.67 (#17548) 2023-01-27 10:43:16 -05:00

Deno

Build Status - Cirrus Twitter handle Discord Chat

the deno mascot dinosaur standing in the rain

Deno is a simple, modern and secure runtime for JavaScript and TypeScript that uses V8 and is built in Rust.

Features

  • Secure by default. No file, network, or environment access, unless explicitly enabled.
  • Supports TypeScript out of the box.
  • Ships only a single executable file.
  • Built-in utilities.
  • Set of reviewed standard modules that are guaranteed to work with Deno.

Install

Shell (Mac, Linux):

curl -fsSL https://deno.land/install.sh | sh

PowerShell (Windows):

irm https://deno.land/install.ps1 | iex

Homebrew (Mac):

brew install deno

Chocolatey (Windows):

choco install deno

Scoop (Windows):

scoop install deno

Build and install from source using Cargo:

cargo install deno --locked

See deno_install and releases for other options.

Getting Started

Try running a simple program:

deno run https://deno.land/std/examples/welcome.ts

Or a more complex one:

const listener = Deno.listen({ port: 8000 });
console.log("http://localhost:8000/");

for await (const conn of listener) {
  serve(conn);
}

async function serve(conn: Deno.Conn) {
  for await (const { respondWith } of Deno.serveHttp(conn)) {
    respondWith(new Response("Hello world"));
  }
}

You can find a deeper introduction, examples, and environment setup guides in the manual.

The complete API reference is available at the runtime documentation.

Contributing

We appreciate your help!

To contribute, please read our contributing instructions.