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
..
bench.js	feat(ext/ffi): Make External pointers keep reference to V8 buffer (#17955)	2023-03-05 08:01:23 +00:00
event_loop_integration.ts	test(ext/ffi): Increase timeout value in event loop integration test callback (#18394)	2023-03-25 09:18:41 +02:00
ffi_types.ts	feat(unstable): Improve FFI types (#20215)	2023-08-21 13:36:26 +05:30
integration_tests.rs	feat: granular --unstable-* flags (#20968)	2023-11-01 23:15:08 +01:00
test.js	chore: upgrade deno_core (#21036)	2023-11-01 20:25:09 +01:00
thread_safe_test.js	chore: update to Rust 1.71 (#19822)	2023-07-13 15:16:24 -06:00
thread_safe_test_worker.js	fix(test_ffi): thread_safe_callback is flaky (#19640)	2023-06-28 14:41:59 -06:00