Skip to content
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

Any plan to support Node.js? #123

Open
Asuka109 opened this issue Jun 2, 2023 · 2 comments
Open

Any plan to support Node.js? #123

Asuka109 opened this issue Jun 2, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@Asuka109
Copy link

Asuka109 commented Jun 2, 2023

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.

@vincentdchan
Copy link
Collaborator

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.

@vincentdchan vincentdchan added the enhancement New feature or request label Jun 26, 2023
@septatrix
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants