Tooling & Developer Experience (DX)

This section covers essential tools that enhance the developer workflow, enforce code quality standards, manage dependencies, structure projects (like monorepos), leverage AI assistance, and ensure consistent development environments.

Essential for maintaining code quality, enforcing coding standards, and catching potential errors early. Highly configurable with a vast ecosystem of plugins and presets. Adopted as the standard linter across all frontend projects.

Eliminates debates about code style by automatically formatting code according to a consistent standard. Improves readability and reduces cognitive load when switching between projects or collaborating. Adopted universally for code formatting.

Comes standard with Node.js, universally understood. While pnpm is preferred, npm remains adopted as the baseline and fallback package manager.

Offers significant improvements in installation speed and disk space usage compared to npm by using a content-addressable store. Provides strictness that prevents phantom dependency issues. Adopted as the preferred standard for its efficiency benefits.

Checkstyle helps prevent style drift and reduces review noise by enforcing agreed conventions automatically. Adopt it as a baseline quality gate in JVM projects, tuned to rules that support readability and maintainability rather than personal preferences.

PMD complements formatting and style checks by flagging problematic patterns (complexity, error-prone constructs, maintainability issues). Use it as part of the standard quality toolchain to keep technical debt from silently accumulating.

Spotless enforces formatting as part of the build, making it easy to keep style consistent across IDEs and contributors. It’s especially effective when paired with other quality gates (Checkstyle/PMD) to separate “format” from “logic” in code reviews.

Lombok can significantly cut repetitive code and make models and DTOs cleaner. Use it intentionally and consistently, and be mindful of team conventions and IDE/tooling setup so the generated code remains transparent to contributors.

jirutka rsql-parser provides a well-known, reusable foundation for “advanced filtering” endpoints (e.g., search screens, admin panels). It helps keep APIs consistent across services and avoids each team reinventing filtering logic and grammar.

Tika shines when you receive heterogeneous files (PDFs, Office docs, images with embedded text/metadata, etc.) and need a unified extraction approach. It’s in TRIAL so we can standardize patterns (performance, security scanning, handling malformed files) before recommending it broadly.

CommonMark-java supports standardized Markdown behavior (CommonMark spec), making it a good choice when services need to transform or sanitize Markdown consistently. It’s in TRIAL while we confirm usage patterns and ensure it fits our rendering/safety needs.

json-path can simplify test assertions and payload inspection without writing lots of parsing code. It’s in TRIAL to validate conventions and avoid overusing it in production logic where stronger typing or clearer models may be preferable.

Developed by Vercel, Turborepo focuses specifically on high-performance build caching within monorepos. Assessing its capabilities, ease of use, and suitability for our potential monorepo needs, especially given its focus compared to more comprehensive tools previously assessed.

The project is deprecated and unmaintained. The official migration path is to ESLint, which now provides comprehensive TypeScript linting capabilities via the @typescript-eslint project. Continued use of TSLint poses risks and lacks support for modern TypeScript features.