type: decision
status: active
timestamp: 2026-06-22
tags: [decision, libraries, community, max-deps, supersedes]

Maximum libraries policy — reverse 'minimal-libraries'; consume community libs heavily

Maximum libraries policy, minimal-libraries reversed MAXIMUM number of community libraries so we write less code ourselves. Every `@chirag127/oriz-*` and `@chirag127/astro-*` package internally uses community libraries as much as possible. Goal: 90% community code / 10% glue. Performance impact mitigated by Astro per-route island hydration + tree-shaking + lazy-load.

Maximum libraries policy

Reversal

User mandate (2026-06-22 evening): “We are not deleting the minimal library use, we are choosing the maximum library use. We will use maximum number of libraries so that we have lesser and lesser number of handwritten code. In our repositories, everything is taken on from the community libraries. And from our own generated libraries, and our own generated libraries will also use the community libraries as much as possible.”

This SUPERSEDES minimal-ui-library-set.md (which itself superseded max-ui-library-set.md earlier the same day). Net effect: back to maximum libraries, with performance mitigation via lazy-load + tree-shake.

Adopted libraries (re-confirmed)

UI primitives

Icons

Charts

Animation

Forms

State + Data

Tables

Date + time

DnD

Toasts + modals

Editor

PDF + image

Audio + video

Markdown + content

Why this works for performance

Our own packages: also lean on community

Every @chirag127/oriz-* and @chirag127/astro-* package wraps community libraries — does NOT re-implement. Examples:

Cross-refs


Edit on GitHub · Back to index