My issue is the current custom compile option limits you to the amalgamation and sticks you with a specific set of compile options.

This is an issue with extensions thst rely on external libraries like the included ICU unicode extension. I have to manually edit the gypi files to get it to compile with the libraries and work with out crashing.

Dynamic library inclusion would fix this issue.

This would be really helpful and I would like to bump this suggestion.

The current configuration is difficult to use with pnpm based projects. It requires monkey patching to get the --build-from-source option to work and is not persistent across new better-sqlite3 releases. Even the npm solution is less than ideal.

It would be nice if better-sqlite3:

• defaulted to dynamically linking the system sqlite3 library which most have,
• allowed the user to specify at runtime the location of an alternate sqlite3 library to load,
• only downloaded and compiled as a last resort.

The current build system also seems to limit the user to the amalgamation.

There are already eetf format de/serialization crates for rust. In the likely event they don't.