Business logic with ease
Effector follows five basic principles:
- Application stores should be as light as possible - the idea of adding a store for specific needs should not be frightening or damaging to the developer.
- Application stores should be freely combined - data that the application needs can be statically distributed, showing how it will be converted in runtime.
- Autonomy from controversial concepts - no decorators, no need to use classes or proxies - this is not required to control the state of the application and therefore the api library uses only functions and plain js objects
- Predictability and clarity of API - a small number of basic principles are reused in different cases, reducing the user's workload and increasing recognition. For example, if you know how .watch works for events, you already know how .watch works for stores.
- The application is built from simple elements - space and way to take any required business logic out of the view, maximizing the simplicity of the components.
npm add effector
To getting started read our article how to write React and Typescript application.
npm add effector effector-react
npm add effector effector-vue
Svelte works with effector out of the box, no additional packages needed. See word chain game application written with svelte and effector.
For additional information, guides and api reference visit our documentation site
You can try effector with online playground
Code sharing, Typescript and react supported out of the box. Playground repository
Use effector-logger for printing updates to console, displaying current store values with ui or connecting application to familiar redux devtools
More examples in documentation
Below are the reference links:
|1.||Read more here.|
|2.||Follow code author here.|