This is looking really good so far.

What do you think about usingBindingSpec type instead ofunknown[] | Record<string, unknown> in theStatement params:

exporttypeStatement={sql:string;params:unknown[]|Record<string,unknown>;};

TheBindingSpec is thebind type indb.exec:

Referenced from SQLite wasm:
https://github.com/sqlite/sqlite-wasm/blob/31e4b6e478a3f10a11b477feb08f1e54b53c791a/index.d.ts#L318

• I have a updated the named parameters extraction method for all cases with more tests.
• I have add tests for the numbered positional parameters?NNN.
• The last commit is just for testing the sqlite/wasmBindable types (we can revert it if it's out of this PR scope).

• I have a updated the named parameters extraction method for all cases with more tests.
• I have add tests for the numbered positional parameters?NNN.
• The last commit is just for testing the sqlite/wasmBindable types (we can revert it if it's out of this PR scope).

We can also export thenormalizeNamedParams as a helper function and give the user the option to chose if he wants to use the helper function of provide a valid named parameters object:

// Use the `normalizeNamedParams` helper functionawaitsql('INSERT INTO groceries (name) VALUES (:name)',normalizeNamedParams({name:'bread'}));// Or provide a valid binding object insteadawaitsql('INSERT INTO groceries (name) VALUES (:name)',{':name':'bread'});

This provide more flexibility, but may introduce some confusion.