@ilokesto/store
v2.0.0
A small framework-neutral state container with synchronous reads and selector subscriptions.
Support: Framework-neutral
ilokesto
[iloˈkɛsto]
Small tools. Explicit contracts.
Build predictable front ends, one focused package at a time.
ilokesto means “toolbox” in Esperanto. Choose only the state, forms, layered UI, rendering, or HTTP tools your product needs.
The toolbox
Start with what you are building.
Each package has one job. Use the groups and comparisons below to find the smallest useful starting point.
State and input
Own application values, connect them to a framework, or manage form interaction.
@ilokesto/state
v2.0.0
Framework adapters, reducers, middleware, and utilities built on the same store model.
Support: Vanilla · React · Vue · Angular · Svelte · Solid
@ilokesto/form
v2.0.0
Headless form state, validation flow, field metadata, and bindings for four UI frameworks.
Support: Vanilla · React · Vue · Svelte · Solid
Layered interface
Build a custom overlay runtime or choose a focused modal or toast system.
@ilokesto/overlay
v2.0.0
A provider-scoped React runtime for custom modals, toasts, sheets, and layered UI.
Support: React
@ilokesto/modal
v2.0.0
A pre-built modal system using Overlay’s shared lifecycle and adapter model.
Support: React
@ilokesto/toast
v2.0.0
Toast notifications with motion, positioning, and auto-dismiss semantics.
Support: React
Standalone rendering and data
Choose React rendering utilities or an OpenAPI-aware ky client without adding another ilokesto package.
@ilokesto/utilinent
v1.2.0
Composable React utilities for conditionals, lists, async states, slots, and lazy UI.
Support: React
@ilokesto/fetcher
v1.0.0
An OpenAPI-aware ky wrapper with typed routes, inferred responses, and errors as results. Available in beta.
Support: Framework-neutralBeta
Two useful distinctions
Choose the right level of abstraction.
01
Store or State?
Choose Store for a framework-neutral value with direct reads and subscriptions. Choose State when you also need framework adapters, reducers, middleware, or state utilities.
02
Overlay or Modal / Toast?
Choose Overlay when you are defining custom layered UI and its adapters. Choose Modal or Toast when that interaction already matches the focused system you need.