Libraries

Hyper-Dank packages are small shared contracts for Hono, HTMX, Bun, and server-rendered JSX apps. They keep mechanics reusable while product behaviour stays in the consuming application.

Library docsLibraries

The libraries deliberately stop at reusable boundaries: component primitives, database lifecycle contracts, Hono/HTMX transport helpers, and script automation. App-owned language, routes, permissions, schemas, repositories, fixtures, and release choices stay local.

Install all packages from npm:

npm install \
  @macavitymadcap/hyper-dank-ui \
  @macavitymadcap/hyper-dank-data \
  @macavitymadcap/hyper-dank-transport \
  @macavitymadcap/hyper-dank-automation
npm install hono typescript

For TypeScript, Hono JSX, CSS import, optional peers, and a minimal package smoke, see Consumer setup. For the first public package set, registry integrity hashes, and trusted-publishing approval notes, see Publication evidence.

Components and CSS UI package @macavitymadcap/hyper-dank-ui Server-rendered Hono JSX primitives, HTMX-friendly props, and a small baseline CSS export. Lifecycle and migrations Data package @macavitymadcap/hyper-dank-data Provider shapes, migration helpers, and Bun conformance tests for app-owned adapters. Hono and HTMX Transport package @macavitymadcap/hyper-dank-transport Form parsing, route parameters, safe error messages, and HTMX-aware redirects. Bun scripts Automation package @macavitymadcap/hyper-dank-automation Shared process, GitHub, verification, server, screenshot, PR-image, and a11y helpers.

Package	npm
`@macavitymadcap/hyper-dank-ui`	npm package
`@macavitymadcap/hyper-dank-data`	npm package
`@macavitymadcap/hyper-dank-transport`	npm package
`@macavitymadcap/hyper-dank-automation`	npm package

Shared Boundaries

Package	Owns	Leaves to Apps
UI	Generic JSX components, class contracts, HTMX prop surfaces, baseline CSS.	Product layout, feature organisms, wording, route paths, permissions.
Data	Provider lifecycle types, migration store contract, ordered migration runner, lifecycle tests.	Domain schemas, repositories, adapter setup, transaction policy.
Transport	Request form helpers, route parameter normalisation, safe error strings, action redirects.	Auth, permissions, services, validation rules, route composition.
Automation	Script mechanics for processes, GitHub, checks, local servers, browsers, PR screenshots, Pa11y.	App fixtures, smoke journeys, deployment targets, release decisions.

Consumption Pattern

Use a package when it removes repeated mechanics without hiding the app contract. Keep imports close to the consuming boundary, add app-specific wrappers only when they clarify product behaviour, and cover package use through consumer-style compatibility tests.