-
Notifications
You must be signed in to change notification settings - Fork 85
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
Access a WASIX instance's filesystem #334
Conversation
…rve the wasm types polyfill
…put from Web Workers can be captured
⏱ Workflow Timer ⏱ Make sure you keep an eye on build times! The goal is to keep CI times under 10 minutes so developers can maintain a fast edit-compile-test cycle.
🤖 Beep. Boop. I'm a bot. If you find any issues, please report them to https://github.com/Michael-F-Bryan/workflow-timer. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great, let's merge!
This adds the ability to mount directories and access the filesystem of a running WASIX instance.
Instead of creating a single
FileSystem
class, I've set things up so you need to pass in a dictionary of mountedDirectory
objects. Most packages will include their own volumes, so allowing users to pass in a singleFileSystem
class which represents the WASIX instance's entire file system when spawning instances will make it really easy to shoot themselves in the foot by clobbering something important (see wasmerio/wasmer#4248).Users are given the ability to create either an empty
Directory
(wrapper aroundTmpFileSystem
) via its constructor or leverage the browser's File System API.