![](\"images/logo.svg\"){kind=logo}
\n\n \n
![\"Browser](\"images/browser_support.png\")
\n\n**NEWS:** `react-easy-state` is moved under `@risingstack/react-easy-state` on npm with **no breaking changes**. Please switch to the new package to get the latest features and bug fixes. Thanks!\n\nstore as early as possible.this keyword in the methods of your state stores.view - including class and function ones - even if they don't seem to directly use a store.Name: {user.name}
);\n\n// DON'T DO THIS\n// This won't re-render on appStore.user.name = 'newName' like mutations\nconst Profile = ({ user }) =>Name: {user.name}
;\n```\n\nview implements an optimal shouldComponentUpdate (or memo) for your components.view as the latest (innermost) wrapper when you combine it with other Higher Order Components.useState - in function components, Easy State won't interfere with them. Consider using autoEffect instead of the useEffect hook for the best experience though.setState in your class components, Easy State won't interfere with it.state. It may conflict with linter rules, which guard against direct state mutations.getDerivedStateFromProps).![\"\"/](\"https://avatars3.githubusercontent.com/u/6956014?v=4\") Miklos Bertalan 💻 ⚠️ 📖 📝 | \n ![\"\"/](\"https://avatars3.githubusercontent.com/u/14181908?v=4\") Roland 💻 ⚠️ 📖 | \n ![\"\"/](\"https://avatars3.githubusercontent.com/u/22714514?s=460&u=cbbc2326d5f671693a1f33671d9eadad902d5191&v=4\") Daniel Gergely 💻 🎨 💡 | \n ![\"\"/](\"https://avatars1.githubusercontent.com/u/7130689?v=4\") Peter Czibik 🚇 | \n
\n \n
\n\n**NEWS:** v6.3.0 fixed a nasty bug that could render [zombie children](https://react-redux.js.org/api/hooks#stale-props-and-zombie-children). Please update to this version at least to save yourself some headaches. Thanks!\n\nstore as early as possible.this keyword in the methods of your state stores.view - including class and function ones - even if they don't seem to directly use a store.Name: {user.name}
);\n\n// DON'T DO THIS\n// This won't re-render on appStore.user.name = 'newName' like mutations\nconst Profile = ({ user }) =>Name: {user.name}
;\n```\n\nIf you are **100% sure** that your component is not using any stores you can skip the `view` wrapper.\n\n```jsx\nimport React from 'react';\n\n// you don't have to wrap this component with `view`\nexport default (() =>This is just plain text
);\n```\n\n`view` wrapping is advised even in these cases though.\n\n- It saves you from future headaches as your project grows and you start to use stores inside these components.\n- `view` is pretty much equivalent to `memo` if you don't use any stores. That is nearly always nice to have.\n\nview implements an optimal shouldComponentUpdate (or memo) for your components.view as the latest (innermost) wrapper when you combine it with other Higher Order Components.useState - in function components, Easy State won't interfere with them. Consider using autoEffect instead of the useEffect hook for the best experience though.setState in your class components, Easy State won't interfere with it.state. It may conflict with linter rules, which guard against direct state mutations.getDerivedStateFromProps).Miklos Bertalan 💻 ⚠️ 📖 📝 | \n Roland 💻 ⚠️ 📖 | \n Daniel Gergely 💻 🎨 💡 | \n Peter Czibik 🚇 | \n
\n \n
\n\n**NEWS:** v6.3.0 fixed a nasty bug that could render [zombie children](https://react-redux.js.org/api/hooks#stale-props-and-zombie-children). Please update to this version at least to save yourself some headaches. Thanks!\n\nstore as early as possible.this keyword in the methods of your state stores.view - including class and function ones - even if they don't seem to directly use a store.Name: {user.name}
);\n\n// DON'T DO THIS\n// This won't re-render on appStore.user.name = 'newName' like mutations\nconst Profile = ({ user }) =>Name: {user.name}
;\n```\n\nIf you are **100% sure** that your component is not using any stores you can skip the `view` wrapper.\n\n```jsx\nimport React from 'react';\n\n// you don't have to wrap this component with `view`\nexport default (() =>This is just plain text
);\n```\n\n`view` wrapping is advised even in these cases though.\n\n- It saves you from future headaches as your project grows and you start to use stores inside these components.\n- `view` is pretty much equivalent to `memo` if you don't use any stores. That is nearly always nice to have.\n\nview implements an optimal shouldComponentUpdate (or memo) for your components.view as the latest (innermost) wrapper when you combine it with other Higher Order Components.useState - in function components, Easy State won't interfere with them. Consider using autoEffect instead of the useEffect hook for the best experience though.setState in your class components, Easy State won't interfere with it.state. It may conflict with linter rules, which guard against direct state mutations.getDerivedStateFromProps).Miklos Bertalan 💻 ⚠️ 📖 📝 | \n Roland 💻 ⚠️ 📖 | \n Daniel Gergely 💻 🎨 💡 | \n Peter Czibik 🚇 | \n
\n \n
\n\n**NEWS:** v6.3.0 fixed a nasty bug that could render [zombie children](https://react-redux.js.org/api/hooks#stale-props-and-zombie-children). Please update to this version at least to save yourself some headaches. Thanks!\n\nstore as early as possible.this keyword in the methods of your state stores.view - including class and function ones - even if they don't seem to directly use a store.Name: {user.name}
);\n\n// DON'T DO THIS\n// This won't re-render on appStore.user.name = 'newName' like mutations\nconst Profile = ({ user }) =>Name: {user.name}
;\n```\n\nIf you are **100% sure** that your component is not using any stores you can skip the `view` wrapper.\n\n```jsx\nimport React from 'react';\n\n// you don't have to wrap this component with `view`\nexport default (() =>This is just plain text
);\n```\n\n`view` wrapping is advised even in these cases though.\n\n- It saves you from future headaches as your project grows and you start to use stores inside these components.\n- `view` is pretty much equivalent to `memo` if you don't use any stores. That is nearly always nice to have.\n\nview implements an optimal shouldComponentUpdate (or memo) for your components.view as the latest (innermost) wrapper when you combine it with other Higher Order Components.useState - in function components, Easy State won't interfere with them. Consider using autoEffect instead of the useEffect hook for the best experience though.setState in your class components, Easy State won't interfere with it.state. It may conflict with linter rules, which guard against direct state mutations.getDerivedStateFromProps).Miklos Bertalan 💻 ⚠️ 📖 📝 | \n Roland 💻 ⚠️ 📖 | \n Daniel Gergely 💻 🎨 💡 | \n Peter Czibik 🚇 | \n