javascript-preferred-libraries

Guide JavaScript library selection by evaluating TypeScript friendliness, minimal dependencies, and alignment with existing package.json configurations. Recommendations span HTTP servers, ORMs, testing, date/time, HTTP clients, and validation to ensure a robust application architecture.

Manage dependencies by enforcing best practices during library selection and architectural decisions. Prefer libraries with minimal dependencies, check alignment with existing Architecture Decision Records, and validate category-aware preferences across your tech stack to avoid bloat.

Select an ORM or HTTP server by consulting existing project preferences in package.json, Claude configurations, and ADRs. This ensures chosen libraries are TypeScript-friendly, well-supported, and explicitly aligned with your current architectural constraints and dependencies.

Yes, the library selection approach explicitly works with existing Architecture Decision Records. It respects project preferences by consulting ADRs alongside package.json and Claude configurations to provide recommendations aligned with your established architectural decisions.

Review JavaScript project dependencies during library selection, dependency reviews, and architectural decisions. Evaluate whether current HTTP clients, validation, testing, and date/time libraries enforce TypeScript friendliness and minimal dependencies to prevent tech stack misalignment.