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
The lack of response to TryGhost#1493 has caused a bit of frustration and projects are increasingly turning to vscode-node-sqlite3 as a new maintained fork. One example of a project that is changing to @vscode/sqlite3 is Knex. A pretty popular SQL query builder. See knex/knex#4858 and knex/knex#4866.
It is unclear from https://www.npmjs.com/package/@vscode/sqlite3 and the commits, issues, comments associated with this repo whether this is indeed the intent of microsoft/vscode-node-sqlite3.
Could you clarify your intentions? Can this be considered a new long-term public fork of node-sqlite3?
The lack of response to TryGhost#1493 has caused a bit of frustration and projects are increasingly turning to vscode-node-sqlite3 as a new maintained fork. One example of a project that is changing to @vscode/sqlite3 is Knex. A pretty popular SQL query builder. See knex/knex#4858 and knex/knex#4866.
It is unclear from https://www.npmjs.com/package/@vscode/sqlite3 and the commits, issues, comments associated with this repo whether this is indeed the intent of microsoft/vscode-node-sqlite3.
Could you clarify your intentions? Can this be considered a new long-term public fork of node-sqlite3?