Alexander Prinzhorn

There are also lambda layers, first search result https://github.com/seanfisher/better-sqlite3-lambda-layer (obviously outdated)

Is this the entire log? I think the actual error is missing. Try deleting `node_modules` + `package-lock.json` and install again

This looks like a duplicate of https://github.com/JoshuaWise/better-sqlite3/issues/126, unless you can reproduce this in isolation. I'd try asking on StackOverflow as well. The error message does not look like it's coming...

This works as expected for me: ```js const fs = require('fs'); const betterSQLite3 = require('better-sqlite3'); const incorrectPathToDB = 'nope.db' try { console.log(fs.existsSync(incorrectPathToDB)); let db = new betterSQLite3( incorrectPathToDB, { readonly:...

@JoshuaWise arguably `if(fileMustExist && anonymous)` should throw because they contradict and are incompatible options? Around here somewhere https://github.com/JoshuaWise/better-sqlite3/blob/02c9c250bc77311b08bec574d3d40890c0b17256/lib/database.js#L39-L44

Given that the API of better-sqlite3 is synchronous, how would an `interrupt` API on your end be used? Would you spawn a second thread that calls `sqlite3_interrupt` after a given...

@spazmodius I personally would prefer a more generic approach, so that use-cases such as hitting a button (think DB Browser for SQLite) can cancel a transaction as well Edit: But...

> but the thread doesn't exit immediately and the query still runs to completion. Are you calling `worker.terminate()` from the parent or are you sending a message via `postMessage()` for...

> Yes, but in nodejs, it might be the case that nodejs is failing to terminate properly - ref [nodejs/help#3332](https://github.com/nodejs/help/issues/3332) That sounds unrelated, it's about child processes spawned inside worker...

Here is a minimal working example that shows that you can terminate a worker thread that is stuck in an endless loop in a SQLite query (the same should be...