rematch VS react-redux

Link: https://rematchjs.org/

I use Rematch. It’s built on top of redux but without all the ridiculous boiler plate. I looked into Redux Toolkit but found it still requiring too much unneeded code.

Rematch

Rematch is a nice wrapper on redux. I’d also recommend recoil, not sure if they’re stable yet but I’ve used it in production without any issues. Depends on the complexity of your app, may be overkill using these libraries.

Rematch - this is what I used last time after careful evaluation.

I’ve always found Redux too verbose and cumbersome. Luckily I found Rematch. It is Redux best practices without the boilerplate

I'm working on a Grid component which uses react window to render the cells, Each cell uses 5 HOCs where they each subscribe to the store(I use rematch) with connect and some of the HOCs have selectors where they compute some data with a relatively expensive function. I use lodash compose to merge all the HOCs and use it in the Cell component.

Rematch has been created a few years ago by Shawn McKay and Blair Bodnar, a pair of canadian programmers. It's a tiny but super powerful wrapper around Redux that reduces tons of boilerplate that Redux needs to operate.

Checkout Rematch as a redux implementation. It is build on top of redux, but removes all the horrible boilerplate and keeps the good parts.

I'm using react/react-redux/react-router/react-router-redux.

Reactjs As seen here I am trying to decouple my app's components as much as I can and make them not aware of any storage or action creator. The goal is to have them to manage their own state and call functions to emit a change. I have been told that you do this using props. Considering // Menu.jsximport React from 'react'import { className } from './menu.scss'import Search from 'components/search'class Menu extends React.Component { render () { return ( Home foo bar ) }} And // Search.jsximport React from 'react'import { className } from './search.scss'class Search extends React.Component { render () { let { searchTerm, onSearch } = this.props return ( {searchTerm} onSearch(e.target.value)} value={searchTerm} /> ) }}Search.propTypes = { searchTerm: React.PropTypes.string, onSearch: React.PropTypes.function}export default Search And reading here I see a smart use of Provider and connect and my implementation would look something like this: import { bindActionCreators, connect } from 'redux'import actions from 'actions'function mapStateToProps (state) { return { searchTerm: state.searchTerm }}function mapDispatchToProps (dispatch) { return bindActionCreators({ dispatchSearchAction: actions.search }, dispatch)}export default connect(mapStateToProps, mapDispatchToProps)(Search) Assuming I have a store handling searchTerm as part of the global state. Problem is, where does this code belongs to? If I put it in Search.jsx I will couple actions with the component and more important to redux. Am I supposed to have two different versions of my component, one decoupled and one connect()ed and have to use it? If yes what would my files tree look like? One file per component or a like a make-all-connected.js ? Answer link : https://codehunter.cc/a/reactjs/decoupling-react-components-and-redux-connect

It is in fact a part of react-redux which is used to connects a React component to a Redux store.