![\"Browser](\"images/browser_support.png\")
\n\n\n\n**Breaking change in v6:** the default bundle changed from the ES5 version to the ES6 version. If you experience problems during the build process, please check [this docs section](#alternative-builds).\n\n\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.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).\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.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).\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.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).\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.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).\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.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).\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.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).\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.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).\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.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).\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.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).\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.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).\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.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).\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.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).\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.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).\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.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).\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.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).\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.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).