I doubt such a utility will be integrated. Joshua's philosophy has always been that better-sqlite3 is a thin wrapper around SQLite's core functionalities. Anything else is out-of-scope for the package and would increase repository noise and maintenance cost.

The proposed utility is also not really generic enough, nothing beats writing the actual worker code:

1. What about Database options such as timeout?
2. (What about bind params?) - Looks like this is part of the example in the docs already
3. What about variations such as pluck or raw?
4. What if you need different PRAGMA?
5. What about setting up user-defined functions and virtual tables for the new Database connection?
6. What if you need loadExtension for your queries to run?

What I personally use is https://github.com/piscinajs/piscina . It abstracts away all the details (e.g. maxThreads) and allows me to use the same setup code (for user-defined functions etc.) that I use in the main program. It also supports things like AbortController, which I make heavy use of (e.g. tied to the socket#close event). I wouldn't recommend re-inventing the wheel and use a well tested Worker Threads library. It's a pain to work with their vanilla API.

Great points. I'll make a PR to the docs to recommend that worker lib 👍

@Prinzhorn hit the nail on the head