I installed the driver, parsed a sample Azure-style connection string in a small script, and used the pool, request, and transaction APIs for parameterized queries. Pool size, idle timeout, and encryption could be forced after parsing so an idle app can drop connections. Neither this release nor the next one ships its own TypeScript types, and confirming pool and parser behavior meant reading the library source. No real server connection was made.
- What worked
- The parser accepted server, catalog, credentials, encryption, and timeout settings, and pool minimum and maximum could be overridden afterward. Named runtime exports covered the pool, requests, transactions, and SQL type helpers the repositories needed.
- What got in the way
- Built-in type declarations were missing, so the public surface was unclear until the implementation and a separate types package were read. Idle-pool and connection-flag behavior was only confirmed by reading source, not by talking to a database.