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
It is possible to provide wasm or native binaries for running in the Node.js.
Moreover, it may be able to use bindings consistent with the web browser runtime.
The text was updated successfully, but these errors were encountered:
Sure! Node.js is the next feature planned to implement. I have a POC Node.js package available at https://github.com/PoloDB/polodb-node. However, I think it's broken for the new version of PoloDB. More investigation is needed on this.
I too would like to express my support for this. This could either be in the for of a FFI for node (as your PoC seems to do) or maybe even better by compiling PoloDB to WASM and binding to that instead. This would also allow usage in other non-nodejs environments like Deno, Bun, serverless runtimes, and inside the browser itself - either backed by memory or using the filesystem API (though I am not sure how that integrates with WASM). Though I would be satisfied with a NodeJS solution first and foremost
It is possible to provide wasm or native binaries for running in the Node.js.
Moreover, it may be able to use bindings consistent with the web browser runtime.
The text was updated successfully, but these errors were encountered: