gm-libs - Fourteen Reusable NestJS Packages for Auth, Data and CRUD
Every backend repeats itself: authentication, configuration, CRUD, file storage, background workers, PDF generation, feature flags and audit trails. We built ours once, as fourteen versioned NestJS packages under one scope, and install them into every project we ship. They are ours rather than a registry's, built for our own work, and versioned with the discipline a public library needs anyway: semantic versions, a changelog, and a packed tarball pinned per project so an upgrade is a decision rather than an accident. Library code has to answer requirements nobody has stated yet without breaking whoever depended on yesterday's answer. That constraint is why a new project starts at week three instead of week one.
Love exploring new ideas? Dive into my blog where I share insights, lessons, and experiences from my journey as a developer and entrepreneur. Whether it’s startups, technology, or the developer lifestyle, you’ll find practical tips, thoughtful discussions, and guides to help you learn, build, and grow.
