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.

Sign up for GitHub

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

Jump to bottom

Consider upstreaming to DuckDB Node #19

Open
archiewood opened this issue Oct 16, 2023 · 5 comments
Open

Consider upstreaming to DuckDB Node #19

archiewood opened this issue Oct 16, 2023 · 5 comments

Comments

@archiewood
Copy link
Contributor

archiewood commented Oct 16, 2023 •
edited
Loading

DuckDB nodeJS is now a standalone repo, which might make this easier to integrate.
@archiewood archiewood changed the title Consider upstreaming to DuckDB Consider upstreaming to DuckDB Node Oct 16, 2023
@RandomFractals

This comment was marked as off-topic.

Sign in to view
@RandomFractals

This comment was marked as off-topic.

Sign in to view
@archiewood
Copy link
Contributor Author

Only looking to have an OSS, free option for our users!

@RandomFractals

This comment was marked as off-topic.

Sign in to view
@antonycourtney
Copy link
Contributor

Hi @archiewood -- I've been in touch with DuckDb Labs folks about this. Everyone I've spoken with agrees it would be good for duckdb-async to get upstreamed. It's a matter of doing some (relatively straightforward) reorganizing of the existing NodeJS code, some CI work, and updating some docs. Hopefully the standalone repo for NodeJS will make it a bit easier to do this minor surgery.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@RandomFractals @antonycourtney @archiewood