Developer finds his RabbitMQ library never worked after reconnection, had zero tests

A developer auditing his private RabbitMQ client library discovered that its core feature — surviving a connection drop — had never functioned at all. Despite over 1,200 lines of code, a rich API, and features like channel pooling and circuit breakers, the library contained no tests and multiple critical bugs. Among the flaws: the channel pool was never rebuilt after reconnection, a rate-limiter called a non-existent Set method, and the library would silently call process.exit() on any unhandled rejection in the host application. The developer rebuilt the library from the ground up with a real integration test suite running against an actual RabbitMQ instance to make reliability claims verifiable. The audited and rebuilt library has since been published as @pinceladasdaweb/rabbitmq, with the experience serving as a cautionary tale about untested infrastructure code.