Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FUTURE: stabilize some Deno APIs behind the flag #23906

Closed
bartlomieju opened this issue May 20, 2024 · 1 comment · Fixed by #23968 or #24011
Closed

FUTURE: stabilize some Deno APIs behind the flag #23906

bartlomieju opened this issue May 20, 2024 · 1 comment · Fixed by #23968 or #24011
Assignees

Comments

@bartlomieju
Copy link
Member

We would like to stabilize some of the Deno APIs behind DENO_FUTURE=1 env var, namely:

  • All the file system APIs available in ext/fs
  • WebGPU APIs in ext/webgpu
  • Deno.dlopen and related APIs in ext/ffi

In other words, we don't want to perform check_unstable() calls in these APIs if DENO_FUTURE=1 env var is present.

This requires two separate changes:

  1. For FS and FFI APIs we need to properly set up the unstable checker in cli/factory.rs to enable these two APIs if DENO_FUTURE is present
  2. For the WebGPU API you want to enable it in exposeUnstableFeaturesForWindowOrWorkerGlobalScope in 99_main.js if the future setting in runtimeOptions is set to true.

We should add a single integration test that checks all these APIs being present without --unstable-* flags but with DENO_FUTURE=1 env var.

Skip changing type declarations for now.

iuioiua added a commit that referenced this issue May 27, 2024
Closes #23906

---------

Co-authored-by: Asher Gomez <ashersaupingomez@gmail.com>
@ry
Copy link
Member

ry commented May 28, 2024

webgpu and ffi not done yet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants