Closed jesus-ale43 closed 1 year ago
Thanks for the issue!
I think I can diagnose at least half of the problem here. Because of different OS APIs, the library dynamically imports either the unix or windows implementation of the underlying IPC client. It looks like the wasm matches neither windows
nor unix
.
That alone could be fixed. However, I did some testing myself, and found that there are several issues that I do not see a solution for:
windows
vs WASM on unix
, it would be difficult to work around thisUnixStream
struct and Windows needs extended open options). Cross compiling to WASM makes it impossible to use these, since they are not made available for its target OS. And, since they work so differently across different systems, I don't see a way to make this possibleAll that said, I'd love to make it work. If there's something I missed that solves all of the points I listed, I'll make it work. But, as far as I can see, there's no clear way to solve your issue, unfortunately. Sorry for the inconvenience :(
I am trying to make a plugin for the
Lapce
editor, it compiles plugins to WASI (WebAssembly System Interface). Because the editor is relatively new, there is not much information about plugin development.The problem is, when I use the package, and compile it to WASI, returns 2 errors:
This is the code I am compiling:
Or you can also look at the repository.