-
Notifications
You must be signed in to change notification settings - Fork 31.1k
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
stabilization of node:sqlite module #57445
Comments
As far as officially stabilizing the module goes, I think there is still some work to do. I think targeting Node v25 in October could be a realistic goal, but there aren't a lot of people working on the effort. Another hurdle is a lack of reviews from collaborators - things move slowly when it takes roughly a week to get changes merged. |
Is there a rough list of what needs done before it can be marked stable? If it's not stable by v24 could it be backported to 24 (and ideally older versions). One of the reasons I want this stabilized soon is so it can be used by libraries / apps with lower minimum supported node versions. |
These are not always readily visible. If there are specific PRs please tag me and I'll be happy to review. |
Not exactly. There are currently some open issues and PRs. Some (not all) of those need to be resolved. I know that @billywhizz had mentioned some potential performance optimizations as well that I think would be good to explore.
I don't see it making the v24.0.0 cutoff, but it could likely be backported. |
i can take a look at any work that is outstanding over next few days and can hopefully help with any effort to stabilize this going forward. |
What is the problem this feature will solve?
I couldn't find any issues tracking the stabalization of the node:sqlite module. Built in sqlite support will remove the need for native modules which complicate build and distribution.
What is the feature you are proposing to solve the problem?
Eventually stabilizing test sqlite
What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: