Lerna is a monorepo management tool for JavaScript/TypeScript projects that provides CLI commands for versioning, publishing, and managing multiple packages from a single repository. It features a modular architecture with separate command implementations, core utilities for project graph construction and dependency resolution, and integration with Nx for task caching and distributed execution. The tool supports both fixed and independent versioning modes, conventional commits for automated changelogs, and works with multiple package managers (npm, yarn, pnpm, bun).
This monorepo provides a suite of libraries and CLI tools for generating changelogs from git metadata according to the Conventional Commits specification. The core pipeline consists of: a git client to fetch commits, a parser to extract structured data from commit messages, a filter to remove reverted commits, and a writer to render the changelog in Markdown. Additional packages handle version bump recommendations, preset loading (Angular, Conventional Commits), and template rendering. The system is designed for both programmatic use via builder-style APIs (e.g., `ConventionalChangelog`, `Bumper`) and direct CLI invocation. It supports multiple git hosting platforms (GitHub, GitLab, Bitbucket) and is configured through presets that define commit type effects, reference formatting, and section ordering. The architecture is a monorepo with 11+ independently published packages, each with its own tests, TypeScript definitions, and CLI entry points. The codebase is actively maintained, with frequent releases, breaking changes managed through major version bumps, and a migration from Handlebars to render functions. It requires Node.js >= 22 and is fully ESM. The project also includes a documentation website (Astro/Starlight), CI/CD via GitHub Actions, and an AI agent skill for commit message guidance. While primarily a developer tool, the repository demonstrates strong software engineering practices: clean separation of concerns, stream-based processing for large commit histories, a preset plugin pattern, and comprehensive test coverage including real git repository interactions. The lower-level packages (parser, filter, writer, git client) are designed to be reusable in other contexts, and the template utilities provide a foundation for custom changelog formatting.
VoucherVault is a self-hosted Django web application for digitally managing vouchers, gift cards, coupons, and loyalty cards. It provides a full CRUD interface with features like barcode/QR code scanning, expiry notifications via Apprise, multi-currency support via Fixer.io, offline-first capabilities (service worker + IndexedDB sync), OIDC authentication, item sharing between users, and a PWA manifest for mobile installation. The architecture is a monolithic Django app with Celery for background tasks (expiry checks), Redis as a message broker, and optional PostgreSQL or SQLite databases. The frontend uses the NiceAdmin Bootstrap template with custom dark mode and charting via ECharts. The codebase is well-organized with clear separation of concerns (models, views, forms, templates, static assets) and includes internationalization for English, German, French, and Italian. While the application is feature-rich and actively maintained, it lacks automated tests and has some code duplication in templates, which limits its quality score.
This repository contains the official Conventional Commits specification website, built with Hugo and a custom theme. It is a static documentation site with multi-language support (29 languages) across multiple specification versions (v1.0.0 and several beta releases). The site is deployed via Netlify with a Docker-based build pipeline. The codebase is primarily HTML/CSS/JS assets and Hugo layout templates, with no application logic, APIs, or data processing. The specification itself is the core content, presented as markdown files organized by version and language. While the theme demonstrates decent SCSS architecture and a language switcher, the overall codebase is simple and tightly coupled to the spec content, offering limited reusability beyond similar documentation sites.