Palistor just landed on npm. npm install palistor — and your React screens stop being a tangle of useEffect.
⚠️ Heads up: Palistor is still an experimental technology. Kick the tires, break it, tell us what hurts.
The one idea
AI is bad at architecture — but it's great at filling declarative slots.
So Palistor removes the architecture task entirely. It splits your frontend into three clean layers:
- View — pure JSX. So primitive there's nowhere to make a mistake.
- ViewModel — one flat config object with behavior (validation, conditional fields, cross-field rules).
-
Model — any data source you plug in via
resolve. Palistor defines the interface, not the implementation.
🤖 Why it's AI-friendly
Here's the punchline: generated code can't fall apart, because there's nowhere for it to go wrong.
Reviewing an AI-written screen becomes reviewing one flat object instead of a tree of useEffects, custom hooks and contexts. You keep control — even when you don't read every line the model wrote. That's the path toward generating real enterprise frontends without losing the plot.
What you get
- ⚡ Granular re-renders — a component subscribes only to the fields it read
- 🧮 Computed field state —
isVisible,isRequired, labels, errors recomputed from the config - 🔌 Async resolvers — auto-tracked deps, retry, optimistic updates, Suspense
- 📋 Lists & entities — normalized registry, list proxy, per-entity templates
- 🪜 Flows — step wizards with branching and per-step validation
- 💾 Persist, i18n, field mapping — batteries included
npm install palistor # peer: react ^19
Live playground with every example: projectint.github.io/palistor
Source & README: github.com/ProjectINT/palistor
Built by Yuri Palienko. MIT licensed.
It's early, it's experimental, and it's fun. Go break it. 🔨
Top comments (0)