Consider using `node:sqlite`

[double-daruma]

Deno (and node.js) now have built in support for sqlite3 with the same module. The benefit of using this built in module is that real sqlite will be used whereas x/sqlite that is currently used has weaker consistency guarantees. This might also allow this gleam library to work on node.js.

[lpil]

Could be good!

[Comamoca]

Hello!
I’m currently developing a new JavaScript FFI for sqlight.

This FFI is compatible with the node:sqlite module for both Node.js and Deno, and all tests pass using the following commands.

gleam test --target javascript --runtime node
gleam test --target javascript --runtime deno

Since this FFI relies on the node:sqlite package for Node.js and Deno and introduces breaking changes, it only works with Node.js v22.5 or later and Deno v2.2 or later.

You can check out the code on this branch.
To use it, add the following configuration to your gleam.toml file:

[dependencies]
sqlight = { git = "https://github.com/Comamoca/sqlight", ref = "feature/node-sqlite" }

[lpil]

Very cool! Would you like to make a PR?

I had a quick look at the code and there's a fairly serious bug in the numbered parameters bit- it can edit the content of strings within the SQL! select '?hello?';

[Comamoca]

Thanks for pointing that out!
I’ll fix the issue and open a PR over the weekend.

[Comamoca]

I investigated the FFI bug over the weekend, and reached the following conclusions.

Regarding the substitution process of ? which caused the bug, this has been fixed in Node.js's node:sqlite, so I have removed the corresponding processing. Therefore, the bug should be resolved.

Comamoca@8a04d3f

As a result, the tests are currently failing in Deno, but this is because Deno has not yet incorporated the latest node:sqlite.

I plan to create a PR once I confirm that Deno has incorporated the latest node:sqlite.
I will likely be able to submit the PR within the year.

[Comamoca]

It's been a while.
Regarding this issue, it seems there's a problem where Deno does not support Named Parameter style SQL statements, so I have created an issue on the Deno side.
denoland/deno#31719

If possible, I would like to submit a PR for this issue, but it is currently undecided whether I can address it.

[lpil]

Thank you for the update 🙏

[Comamoca]

The compatibility issue with node:sqlite is expected to be resolved soon, as a pull request has been created for the corresponding issue.

Additionally, we have confirmed that the FFI code currently implemented passes all tests on Node.js.
Once a version of Deno with the pull request merged is released, we will conduct tests and create a pull request if there are no issues.

[Comamoca]

Happy New Year!

Deno v2.6.4, which includes a bug fix for node:sqlite, was released on January 5, 2026.
I ran the tests using this version of Deno, and all test cases passed on both Node.js and Deno.

❯ gleam test --target javascript --runtime node
   Compiled in 0.02s
    Running sqlight_test.main
(node:113230) ExperimentalWarning: SQLite is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
....................
20 tests, 0 failures

sqlight on  feature/node-sqlite:main [!?⇡] via ⭐ v1.14.0 via ❄️  impure (devenv-shell-env)
❯ gleam test --target javascript --runtime deno
   Compiled in 0.02s
    Running sqlight_test.main
....................
20 tests, 0 failures

Since I have confirmed that the code is working as expected, I am planning to create a Pull Request.

In conjunction with the PR, I am considering updating the CI to run the test code on both Node.js and Deno. Would it be acceptable to include those CI changes in the same PR?

[lpil]

Brilliant! Yes please, that sounds like a really good idea

[Comamoca]

Sorry for the late update, but I opened a PR a couple of days ago.

This PR switches the SQLite client for the JS backend over to node:sqlite. I've also updated the GitHub Actions to include Node.js in the tests.