/**
 * V4 uses React Context Providers to manage shared state across themes, replacing
 * Redux in areas where frequent reactivity is not critical.
 *
 * Context providers are preferred in themes over Redux due to hydration errors
 * introduced by content that relies on Redux state.
 *
 * Providers are split similar to how you would separate state into Redux state
 * slices, with related state and setters being grouped in separate providers.
 *
 * ## Limitations of Context
 *
 * React context is not designed for frequent or granular updates to large or deeply nested
 * state trees. As such, Redux is still the preferred method for managing shared
 * state in admin.
 *
 * Every time a context value changes, all components that consume that context
 * will re-render, even if they only consume a subset of the value. With this in
 * mind, if adding state to a context, consider how often the data will be updated
 * (if at all) and whether a new context provider should be created to avoid
 * affecting consumers of existing providers.
 *
 * @module API Reference/Providers
 */
export { default as AppProvider } from './app-provider';
export { default as PropertiesProvider } from './properties-provider';
export { default as SearchProvider } from './search-provider';
export { default as UserProvider } from './user-provider';
export { default as GlobalConfigProvider } from './global-config-provider';
//# sourceMappingURL=index.d.ts.map