Packages
- @k8ordo/uiReact components, buttons and dialogs included, that you can place in a Server Component. Menus and tooltips open in the top layer through the Popover API, with no
z-indexto tune. - @k8ordo/formA React form library that derives HTML constraint attributes and server-side validation from a zod schema. The constraints are HTML attributes, so the browser checks input before JavaScript loads.
- @k8ordo/stateReads and writes values in the URL, the history entry, localStorage and cookies like
useState. Wherever a value lives, a zod schema types it and one hook handles it. - @k8ordo/routerA React router that switches pages through the Navigation API.
hrefandnavigateToare typed by the route table, and links stay plain<a>elements. - @k8ordo/frameworkA framework that builds a React Server Components app with Vite. The same code becomes an app with no server under
mode: 'static', or one with a server undermode: 'server'. The directories undersrc/routes/are the URLs. - @k8ordo/i18nReact i18n with messages written as functions, called the same way in Server and Client Components. The locale list in
defineLocaleslets the types catch a missing translation. Choosing a language, and adding or removing the locale in a URL, use the same list. - @k8ordo/color-schemeReact dark mode that stores the visitor’s choice in localStorage, resolves it against the OS setting, and puts the
darkclass on<html>. A script in the root layout’s<head>sets thedarkclass before the first paint, and a provider updates it when the OS setting or the saved preference changes.
Shared commitments
Baseline only
A feature is used as soon as all four core browsers ship it (Baseline newly available). We do not wait the further 30 months for widely available. There are no polyfills or fallbacks, so old browsers are not supported.
Always on the latest React
React 19 and Server Components are assumed, and new idioms are adopted as they arrive. No old idioms are kept for compatibility. Every package has one way to write each thing.
TypeScript safe
Wrong usage is a type error as soon as you write it. Docs and generated files are built from the types, so they match the implementation.
Readable by agents
Every package ships its own documentation inside the npm package. An agent reads the docs for the installed version from
node_modules/@k8ordo/<name>/docs/.