You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you use the new Directory() constructor, it will create a temporary in-memory filesystem that is backed by a virtual_fs::mem_fs::FileSystem.
In #337, I'm adding a static Directory.fromBrowser() function which will create a Directory backed by the browser's FileSystem API. That means you'd be able to mount a directory backed by OPFS or the FileSystemDirectoryHandle you get from window.showDirectoryPicker().
That PR hasn't been merged yet, but that's mainly because we chose to implement the easier in-memory version first and add support for the FileSystem API after making @wasmer/sdk public.
Amazing work! Any indication when persistent OPFS will be available? This would allow for such high-demand applications like vector search in the browser by the very popular usearch library.
When you talk about 'FileSystem access' in browsers, does this mean that the data is persistent? Through OPFS or another storage offered by browsers?
Context vincent-herlemont/native_db#65
The text was updated successfully, but these errors were encountered: