UI-independent logic
Keep business rules outside React components and reuse them across multiple views.
Nrgy.jsReactive business logic outside the UI
Build UI-independent state, effects, controllers, and view models on top of a small reactive core.
Skip to content
Start from the right path
Nrgy.js combines a small reactive core with architecture patterns for controllers, view models, lifecycle, and dependency-aware application logic.
- Core primitives
- MVVM patterns
- React integration
- Migration guides
- Recipes
Reading paths
Pick the route that matches your current task instead of guessing where to start.
New to Nrgy.js
Introduction -> Quick Start -> Core -> MVVM and Controllers
Designing an app architecture
Architecture -> MVVM and Controllers -> Integrations -> Recipes
Migrating from older versions
What you can build
The docs focus on practical application structure, not only isolated API calls.
Screen view models
Keep screen state, actions, and loading flows out of the render layer.
Shared business controllers
Reuse one business flow across multiple views and screens.
Forms with batched updates
Model several fields and coordinated updates without leaking logic into UI.
React + Ditox integration
Wire view models and shared services through explicit dependency boundaries.
Documentation sections
Use the product docs as the main path, then drop into contributing and package references when you need implementation detail.
- Introduction: what Nrgy.js is, what it solves, and how to read the docs
- Core: atoms, computed values, effects, batching, scopes, lifecycle, and scheduler behavior
- Architecture: layering, UI boundaries, reuse strategy, and contracts between layers
- MVVM and Controllers: controller and view-model roles, public contracts, and lifecycle expectations
- Integrations: React bindings, Ditox-based dependency injection, and advanced integrations
- Recipes: concrete examples for view models, shared state, forms, cleanup, and DI
- Migration: legacy concepts, replacement patterns, and import-level migration guidance
- FAQ: short answers about effects, batch, scope, destroy, MVVM, and React usage
- Contributing: workflow, coding style, documentation rules, and agent-facing repository conventions