-
Notifications
You must be signed in to change notification settings - Fork 229
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
feat: support wasm build #673
base: main
Are you sure you want to change the base?
Conversation
The CI setup for notify is totally broken at the moment. But ideally, it would run for multiple toolchains, regardless of the contents of the rust-toolchain.toml file. We want to run the pipelines for the nightly toolchain as well. If you want, you can add a wasm job. I have never worked with wasi and I have no idea how notify should handle a wasi environment. How FS event notification even works there. Would it be possible to implement |
Co-authored-by: Daniel Faust <[email protected]>
Co-authored-by: Daniel Faust <[email protected]>
The wasi implemented the basic std::fs relate API, it worked fine at https://stackblitz.com/.
Yeah. The std::os::wasi::fs::MetadataExt is implement at nightly rust, the stable version hasn't it. If it move into stable version we could implement it. |
We are using
notify
as watcher and build it to wasm32-wasip2 and run it at https://stackblitz.com/.But when using
notify-debouncer-full
to instead ofnotify
, it can't build because theget_file_id
is not implement at wasm. Thestd::os::wasi::fs::MetadataExt
is implement at nightly rust, the stable version hasn't it. So here usingNoCache
for wasm to avoid the issue.I try to add a build wasm32-wasip2 ci, but the rust toolchain version is 1.77.2, it hasn't support the wasm32-wasip2 target.It need to bump rust toolchain at first. If you approved it, please ping me i will upgrade it at first.
Thank your excellent work!