Developer Finds Three Key Bugs Building a Nim Microservice on a Custom Framework Fork

A developer building a single-endpoint contact form microservice for their portfolio site in the Nim language encountered three instructive bugs while dogfooding their own fork of the Mummy web framework. The service, which handles POST requests with name, email, and message validation, also includes CORS middleware, an in-memory rate limiter, and auto-generated OpenAPI documentation. A deployment to Render's free tier revealed that outbound SMTP ports are blocked, forcing a switch to Resend's HTTPS-based REST API instead of standard SMTP. Two additional bugs exposed subtle Nim-specific pitfalls: duplicate HttpHeaders type conflicts caused by different import paths for the same module, and a GC-safety compiler error triggered by a global rate-limiter table that required a workaround using a GC-unsafe pragma. The developer noted that actually deploying and using a framework in production surfaces internals issues that building the framework itself never does.