Popularity

7.3

Stable

Activity

0.0

Declining

Stars 1,965

Watchers 48

Forks 133

Last Commit over 1 year ago

Programming language: JavaScript

License: MIT License

Tags: Code Design Data Store

cerebral alternatives and similar libraries

Based on the "Data Store" category.
Alternatively, view cerebral alternatives based on common mentions on social networks and blogs.

redux

10.0 8.7 cerebral VS redux

Predictable state container for JavaScript apps
react-redux

9.7 8.5 cerebral VS react-redux

Official React bindings for Redux

Appwrite - The Open Source Firebase alternative introduces iOS support

Appwrite is an open source backend server that helps you build native iOS applications much faster with realtime APIs for authentication, databases, files storage, cloud functions and much more!

Promo appwrite.io

reselect

9.5 6.7 cerebral VS reselect

Selector library for Redux
recompose

9.5 1.7 cerebral VS recompose

A React utility belt for function components and higher-order components.
reflux

8.6 0.0 cerebral VS reflux

A simple library for uni-directional dataflow application architecture with React extensions inspired by Flux
mobx-react

8.6 7.4 cerebral VS mobx-react

React bindings for MobX. Create fully reactive components.
effector-react

8.3 9.8 cerebral VS effector-react

Business logic with ease ☄️
alt

8.2 0.0 cerebral VS alt

Isomorphic flux implementation
fluxible

7.3 7.7 cerebral VS fluxible

A pluggable container for universal flux applications.
fluxxor

7.1 0.0 cerebral VS fluxxor

:hammer_and_wrench: Flux architecture tools for React
kea

7.0 6.8 cerebral VS kea

Production Ready State Management for React
redux-batched-actions

5.8 0.0 cerebral VS redux-batched-actions

redux higher order reducer + action to reduce actions under a single subscriber notification
redux-ui

5.1 0.0 cerebral VS redux-ui

Easy UI state management for react redux.
teaful

4.9 1.4 cerebral VS teaful

🍵 Tiny, easy and powerful React state management
shasta

4.9 0.0 cerebral VS shasta

Dead simple + opinionated toolkit for building redux/react applications
redux-batched-subscribe

4.5 0.0 cerebral VS redux-batched-subscribe

store enhancer for https://github.com/reactjs/redux which allows batching subscribe notifications.
react-i13n

4.3 5.7 cerebral VS react-i13n

A performant, scalable and pluggable approach to instrumenting your React application.
baobab-react

3.9 0.0 cerebral VS baobab-react

React integration for Baobab.
fluorine-lib

3.4 0.0 cerebral VS fluorine-lib

Reactive state and side effect management for React using a single stream of actions.
react-controllables

3.3 0.0 cerebral VS react-controllables

Easily create controllable components
react-redux-provide

2.4 0.1 cerebral VS react-redux-provide

Bridges the gap between Redux and the declarative nature of GraphQL/Relay. Share, manipulate, and replicate application state across any number of components.
resourcerer

1.8 5.0 cerebral VS resourcerer

Declarative data-fetching and caching framework for REST APIs with React
react-3ducks

0.8 0.0 cerebral VS react-3ducks

Simple state management solution for React
synergies

0.7 7.9 cerebral VS synergies

Create a performant distributed context state for React by composing reusable state logic.
react-storage-hoc

0.2 8.1 cerebral VS react-storage-hoc

demo
zustand

- cerebral VS zustand

docs

Do you think we are missing an alternative of cerebral or a related project?

Add another 'Data Store' Library

Popular Comparisons

README

Cerebral

A declarative state and side effects management solution for popular JavaScript frameworks

Maintainer needed

https://gist.github.com/christianalfoni/f1c4bfe320dcb24c403635d9bca3fa40

Documentation

Contribute

The entire Cerebral codebase has been rewritten to encourage contributions. The code is cleaned up, commented and all code is in a "monorepo". That means you can run tests across projects and general management of the code is simplified a lot.

Clone the monorepo: git clone https://github.com/cerebral/cerebral.git
In root: npm install

The packages are located under packages folder and there is no need to run npm install for each package.

Using monorepo for your own apps

If you want to use Cerebral 2 directly from your cloned repo, you can create a symlinks for following directories into the node_modules directory of your app:

packages/node_modules/cerebral
packages/node_modules/function-tree
packages/node_modules/@cerebral

If your app and the cerebral monorepo are in the same folder you can do from inside your app directory:

$ ln -s ../../cerebral/packages/node_modules/cerebral/ node_modules/
# ...

Just remember to unlink the package before installing it from npm:

$ unlink node_modules/cerebral
# ...

Running demos

Go to the respective packages/demos/some-demo-folder and run npm start

Testing

You can run all tests in all packages from root:

npm test

Or you can run tests for specific packages by going to package root and do the same:

npm test

Changing the code

When you make a code change you should create a branch first. When the code is changed and backed up by a test you can commit it from the root using:

npm run commit

This will give you a guide to creating a commit message. Then you just push and create a pull request as normal on Github.

Release process

Review and merge PRs into next branch. It is safe to use "Update branch", the commit created by Github will not be part of next history
If changes to repo-cooker, clean Travis NPM cache
From command line:

$ git checkout next
$ git pull
$ npm install # make sure any new dependencies are installed
$ npm install --no-save repo-cooker # needed to test release, make sure you have latest
$ npm run release # and check release notes
$ git checkout master
$ git pull
$ git merge --ff-only next
$ git push

cerebral

Declarative state and side effects management for popular JavaScript frameworks