@kannan19302/ui
v1.0.15
Published
UniERP Design System — one package, subpath exports (PLATFORM_ARCHITECTURE.md § 7.2)
Downloads
198
Readme
unierp-design-system
Part of UniERP — an open-source, self-hostable multi-tenant application platform. Repository map · Architecture · Contributing · Security
Layer L1 — Foundation of the UniERP platform. Depends on: nothing in the workspace.
What this is
Tokens → theme → components → charts → data grid → forms → workflow, plus Storybook. Consumed by three frontends and by partner extensions.
The invariant this repository owns
No dependency on the API or the database. That is what makes "a UI component cannot import a service" structural rather than a lint rule. It is one package with subpath exports, not fourteen — publishing fourteen would create 42 version-coherence problems per release.
The rule that applies everywhere
A repository may depend only on published artifacts of a strictly lower layer — never sideways within a layer, never upward. A cycle is not discouraged; it is unrepresentable, because the lower layer's package cannot name the higher one.
See the platform overview for the full map, and
PLATFORM_ARCHITECTURE.md § 4.2 for
the reasoning.
Licence
AGPL-3.0.
