Consider upstreaming to DuckDB Node

[archiewood]

DuckDB nodeJS is now a standalone repo, which might make this easier to integrate.

[RandomFractals]

suggested as much in less formal terms before:

#8 (comment)

[RandomFractals]

also, @archiewood what are you trying to achieve with your DuckDB SQL Tools driver clone in VS Code marketplace? 🙂

We hope you know that the original will always get the most installs and we do intend to keep it current too! ☮️

[archiewood]

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

[RandomFractals]

We don't think most users actually care to see and dive into cloned vscode extension code while using it, which you reverse engineered from our DuckDB tools share anyway, including cloning some of our DuckDB SQL Tools features docs and bullet points. 😆

Our free DuckDB SQL Tools extension is free and will support DuckDB latest moving forward with less bells and whistles other users can find in our DuckDB Pro Tools.

So, feel free to maintain your clone, but we don't see a value in doing that just because you guys have partnered and fail to recognize the original! 🤗

[antonycourtney]

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.

[hc-12]

Has there been any progress on this matter?

Edit:

I just realised duckdb have released a new library that supports async https://duckdb.org/docs/stable/clients/node_neo/overview.html

Perhaps mark duckdb-async as being deprecated as well?