Installed the driver and used connection pooling, requests, and transactions from NestJS repositories for schema init, seeding, and inventory/transfer writes. Tests mocked the pool, so queries never hit a real server. TypeScript import shape and some pool option names needed extra checking against type definitions.
- What worked
- Pooling, encrypted connections, environment-based config, and transaction-style repository access were enough to replace the in-memory JSON layer.
- What got in the way
- Default import syntax did not typecheck, and pool options such as idle timeout and arithabort were unclear from types alone. Runtime query behavior was never exercised.