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.

Sign up for GitHub

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

Jump to bottom

Support native system access from wasm #2968

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Support native system access from wasm #2968

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift click to select a range
8b1578e
Support native system access from wasm
lucacasonato Mar 5, 2023
f1ed573
update deno
lucacasonato Mar 5, 2023
6f47ff2
deno canary
lucacasonato Mar 16, 2023
29691e9
disable wasm-sys on windows
lucacasonato Mar 16, 2023
c41dc56
no windows support
lucacasonato Mar 16, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
no windows support
  • Loading branch information
@lucacasonato
lucacasonato committed Mar 16, 2023
commit c41dc56d73a41de19f89722709073950b06092c6
4 changes: 4 additions & 0 deletions lib/shared/types.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -640,6 640,10 @@ export interface InitializeOptions {
* "fs" and "process" namespaces must be provided by specifying either a
* namespace containing for "fs" and "process", or specifiers to an ES module that exports these bindings
* as a default export. The former is unsupported when using "worker: true".
*
* The passed "fs" namespace must operate on Unix-style paths. One can thus
* not use this feature to access the local file system on Windows when using
* Node.js' built-in "fs" module.
*/
wasmSystemAccess?: WasmSystemAccess

Expand Down